SKU Based Contract Management in an Electronic Procurement System

ABSTRACT

A single instance, multi-tenant procurement system, includes an access module to provide access to a plurality of end users associated with an organization to their respective accounts, each account being customized by a super user of the organization, a search engine to execute searches for products offered by one or more suppliers, a transaction module to process and track one or more requisitions generated by the plurality of end users, a business rules module to apply business rules established between the organization and the one or more suppliers to process the requisitions, and a data repository to store data generated on the system.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/286,506, “Sku based contract management in an electronic procurementsystem”, filed on Sep. 29, 2008, which is a continuation-in-part of U.S.patent application Ser. No. 12/283,280, “Form Management in anElectronic Procurement System,” filed on Sep. 9, 2008, which is herebyincorporated entirely herein by reference.

This application claims the benefit and priority of U.S. ProvisionalPatent Application Ser. No. 61/130,028, filed on May 27, 2008, which ishereby incorporated entirely herein by reference.

This application is related to U.S. patent application Ser. No.10/318,814, filed Dec. 13, 2002, now U.S. Pat. No. 6,944,613 entitled“Method and System for Creating a Database and Searching the Databasefor Allowing Multiple Customized Views, issued on Sep. 13, 2005, whichis hereby incorporated entirely herein by reference.

This application is related to U.S. patent application Ser. No.12/283,276, “Taxonomy and Data Structure for an Electronic ProcurementSystem” filed on Sep. 9, 2008, (Attorney Docket Number 054848-5003),which is hereby incorporated entirely herein by reference.

This application is related to U.S. patent application Ser. No.12/283,275, “Shopping Cart Management in an Electronic ProcurementSystem” filed on Sep. 9, 2008, (Attorney Docket Number 054848-5004),which is hereby incorporated entirely herein by reference.

This application is related to U.S. patent application Ser. No.12/283,274, “Workflow and Material Management in an ElectronicProcurement System” filed on Sep. 9, 2008, (Attorney Docket Number054848-5005), which is hereby incorporated entirely herein by reference.

This application is related to U.S. patent application Ser. No.12/283,279, “Multi-Currency Normalization In An Electronic ProcurementSystem” filed on Sep. 9, 2008, (Attorney Docket Number 054848-5006),which is hereby incorporated entirely herein by reference.

See CIP reference above.

This application is related to U.S. patent application Ser. No.12/283,277, “Identifying and Resolving Discrepancies Between PurchaseDocuments and Invoices” filed on Sep. 9, 2008, (Attorney Docket Number054848-5008), which is hereby incorporated entirely herein by reference.

This application is related to U.S. patent application Ser. No.12/283,278, “Providing Substitute Items When An Ordered Item IsUnavailable” filed on Sep. 9, 2008, (Attorney Docket Number054848-5009), which is hereby incorporated entirely herein by reference.

This application is related to U.S. patent application Ser. No.12/283,281, “Prioritizing Order And Receipt Of Items Between Users”filed on Sep. 9, 2008, (Attorney Docket Number 054848-5010), which ishereby incorporated entirely herein by reference.

This application is related to U.S. patent application Ser. No.12/283,282, “Invoice Workflow” filed on Sep. 9, 2008, (Attorney DocketNumber 054848-5011), which is hereby incorporated entirely herein byreference.

This application is related to U.S. patent application Ser. No. ______,“Multi-Constituent Attribution of a Vendor's Product Catalog” filed onthe same date as this application, (Attorney Docket Number 054848-5012),which is hereby incorporated entirely herein by reference.

Reference to this application removed.

This application is related to U.S. patent application Ser. No. ______,“Purchase Requisition Importation in an Electronic Procurement System”filed on the same date as this application, (Attorney Docket Number054848-5014), which is hereby incorporated entirely herein by reference.

FIELD OF INVENTION

The present invention relates generally to the field of procurement and,in particular, to a system and method for accessing or creating acontract between a user organization and a supplier or catalog,associating a specific item attribute to the contract, associating aspecific item to the contract using the specific item attribute,determining a specific item to associate with the contract using thespecific item attribute from among a plurality of specific items, andcomparing item price data to the price of the item associated with thecontract, over a network using a single instance system that supportsmulti-tenants in a multi-business to multi-consumer type environment.

BACKGROUND OF INVENTION

Current e-commerce systems and methods provide consumers and businessesthe ability to browse product lines and consummate sales transactions.However, current e-commerce systems do not allow for easy customizationof the needed functionality to facilitate the transaction. While currentsystems can be customized for a specific business or customer, thecustomization is a time consuming and complicated task. Thesecustomizations must generally be hard coded into the application by thedevelopers, thereby incurring increases in costs, delay inimplementation, and loss of productivity. In the field of procurement,for example, an organization in need of a product or service generallyhas contractual relationships with multiple vendors to provide thedesired product or service. The contractual relationship may define suchterms as price, lot size, form of delivery, amount of discount, andother business rules. These rules may become complex as one term mayinfluence other terms, such as different levels of discounts based onthe number of items ordered.

Procurement systems also generally require order authorization from aprocurement officer of the organization or someone in charge ofreviewing the orders for compliance with internal policies of theorganization, in addition to the contractual relationships with thevendors. These orders must be processed and tracked as the ordersprogress through the approval process such that the individuals placingorders are notified of whether the order was approved or denied, as wellas for internal audit purposes.

Furthermore, procurement systems also do not currently provide featuresthat would allow users to access or create a contract between a userorganization and a supplier or catalog, associate a specific itemattribute to the contract, associate a specific item to the contractusing the specific item attribute, determine a specific item toassociate with the contract using the specific item attribute from amonga plurality of specific items, and compare item price data to the priceof the item associated with the contract. Therefore, there is a need fora system and method that can provide an efficient and simple procurementprocess that is easily customizable for multiple organizations andmultiple vendors with simple and complex business terms, and can alsoprovide a single point-of-access for both businesses and consumers tointerface, interact, and implement and execute transactions, inaccordance with existing or newly defined relationships, using a customand configurable methodology for realizing their requirements.

SUMMARY OF THE INVENTION

Accordingly, the present invention is directed to a procurement systemand method over a network using a single instance multi-tenantarchitecture that substantially obviates one or more problems due tolimitations and disadvantages of the related art.

An object of the present invention is to provide a system and methodthat can provide an efficient and simple procurement process that iseasily customizable for multiple organizations and multiple vendors withsimple and complex business terms, and can also provide a singlepoint-of-access for both businesses and consumers to interface,interact, and implement and execute transactions, in accordance withexisting or newly defined relationships, using a custom and configurablemethodology for realizing their requirements.

Additional features and advantages of the invention will be set forth inthe description which follows, and in part will be apparent from thedescription, or may be learned by practice of the invention. Theobjectives and other advantages of the invention will be realized andattained by the structure particularly pointed out in the writtendescription and claims hereof as well as the appended drawings.

To achieve these and other advantages and in accordance with the purposeof the present invention, as embodied and broadly described, a singleinstance, multi-tenant procurement system includes a server systemhosting an electronic procurement system, comprising: an access modulefor receiving a user request for access to the system and grantingaccess to the system; a catalog module for receiving a user request toadd a new item to a database and new item data from the user, whereinthe catalog module stores the new item data in the database for accessby users of the electronic procurement system.

In another aspect, a server system hosting an electronic procurementsystem comprises: an access module for receiving a user request foraccess to the system and granting access to the system; a catalog modulefor receiving a user request to add a new supplier to a database and newsupplier data from the user, wherein the catalog module stores the newsupplier data in the database for access by users of the electronicprocurement system.

In another aspect, a client system communicating with an electronicprocurement system comprises: a client interface for sending a requestfor access to the system and receiving access to the system, wherein theclient interface sends a request to add a new item to a database, andwherein the client interface sends new item data to the system forstorage in the database for access by users of the electronicprocurement system.

In another aspect, a client system communicating with an electronicprocurement system comprises: a client interface for sending a requestfor access to the system and receiving access to the system, wherein theclient interface sends a request to add a new supplier to a database,and wherein the client interface sends new supplier data to the systemfor storage in the database for access by users of the electronicprocurement system.

In another aspect, a server hosting an electronic procurement systemcomprises: an access module for receiving a user request for access tothe system and granting access to the system; a form management modulefor receiving a user request to create a custom form for accessing adatabase, wherein the database stores data associated with items; and amanage privileges module for checking user privileges to determine if auser may create the custom form.

In another aspect, a client system communicating with an electronicprocurement system comprises: a client interface for sending a requestfor access to the system and receiving access to the system, wherein theclient interface sends a request to create a custom form for accessing adatabase that stores items.

In another aspect, a server system hosting an electronic procurementsystem comprises: an access module for receiving a user request foraccess to the system and granting access to the system; and a catalogmodule for receiving a user request to create a custom search field orattribute for searching a database.

In another aspect, a client system communicating with an electronicprocurement system comprises: a client interface for sending a requestfor access to the system and receiving access to the system, wherein theclient interface sends a user request to create a custom search field orattribute for searching a database.

In another aspect, a server system hosting an electronic procurementsystem comprises: an access module for receiving a user request foraccess to the system and granting access to the system; a contractmanagement module for managing a procurement contract between at leastone organization and at least one supplier, wherein the contractmanagement module associates the procurement contract with a group, andwherein the contract management module updates at least the group ifamendments are made to the procurement contract or contractual eventsoccur.

In another aspect, a client system communicating with an electronicprocurement system comprises: a client interface for sending a requestfor access to the system and receiving access to the system, wherein theclient interface receives data for managing a procurement contractbetween at least one organization and at least one supplier, wherein theclient interface sends data for associating the procurement contractwith a group, and wherein a user receives updates using a clientinterface if amendments are made to the procurement contract orcontractual events occur.

In another aspect, a server system comprises: one or more processors;memory; one or more programs stored in the memory, wherein the one ormore programs comprise instructions to, at a server system hosting anelectronic procurement system: receive a user request for access to thesystem; grant access to a user; receive a user request to access orcreate a contract between a user organization and a supplier or catalog;and receive a user request to associate a specific item attribute to thecontract.

In another aspect, a server system comprises: one or more processors;memory; one or more programs stored in the memory, wherein the one ormore programs comprise instructions to, at a server system hosting anelectronic procurement system receive a user request for access to thesystem; grant access to a user; receive a user request to add a item toa shopping cart; and associate the item to a contract.

In another aspect, server system comprises: one or more processors;memory; one or more programs stored in the memory, wherein the one ormore programs comprise instructions to, at a client system communicatingwith an electronic procurement system: sending a user request for accessto the system; receiving access to the system; sending a user request toaccess or create a contract between a user organization and a supplieror catalog; and sending a user request to associate a specific itemattribute to the contract.

In another aspect, a computer-implemented method includes the steps of,at a server system hosting an electronic procurement system: receiving auser request for access to the system; granting access to the system;receiving a user request to add a new item to a database; and receivingnew item data from the user and storing the new item data in thedatabase for access by users of the electronic procurement system.

In yet another aspect, a computer-implemented method includes the stepsof, at a server system hosting an electronic procurement system:receiving a request for access to the system; granting access to thesystem; receiving a request to add a new supplier to a database; andreceiving new supplier data and storing the new supplier data in thedatabase for access by users of the electronic procurement system.

In yet another aspect, a computer-implemented method, comprising at aclient system communicating with an electronic procurement system:sending a request for access to the system; receiving access to thesystem; and sending a request to add a new item to a database andsending new item data to the system for storage in the database foraccess by users of the electronic procurement system.

In yet another aspect, a computer-implemented method includes the stepsof, at a client system communicating with an electronic procurementsystem: sending a request for access to the system; receiving access tothe system; and sending a request to add a new supplier to a databaseand sending new supplier data to the system for storage in the databasefor access by users of the electronic procurement system.

In yet another aspect, a computer-implemented method includes the stepsof, at a server hosting an electronic procurement system: receiving auser request for access to the system; granting access to the system;receiving a user request to create a custom form for accessing adatabase, wherein the database stores data associated with items; andchecking user privileges to determine if a user may create the customform.

In yet another aspect, a computer-implemented method includes the stepsof, at a client system communicating with an electronic procurementsystem: sending a request for access to the system; receiving access tothe system; and sending a request to create a custom form for accessinga database that stores items.

In yet another aspect, a computer-implemented method includes the stepsof, at a server system hosting an electronic procurement system:receiving a user request for access to the system; granting access tothe system; and receiving a user request to create a custom search fieldor attribute for searching a database.

In yet another aspect, a computer-implemented method includes the stepsof, at a client system communicating with an electronic procurementsystem: sending a user request for access to the system; receivingaccess to the system; and sending a user request to create a customsearch field or attribute for searching a database.

In yet another aspect, a computer-implemented method includes the stepsof, at a server system hosting an electronic procurement system:receiving a user request for access to the system; granting access tothe system; managing a procurement contract between at least oneorganization and at least one supplier; associating the procurementcontract with a group; and updating at least the group if amendments aremade to the procurement contract or contractual events occur.

In yet another aspect, a computer-implemented method includes the stepsof, at a client system communicating with an electronic procurementsystem: sending a request for access to the system; receiving access tothe system; managing a procurement contract between at least oneorganization and at least one supplier; associating the procurementcontract with a group; and receiving updates if amendments are made tothe procurement contract or contractual events occur.

In yet another aspect, a computer-implemented method includes the stepsof, at a server system hosting an electronic procurement system:receiving a user request for access to the system; granting access to auser; receiving a user request to access or create a contract between auser organization and a supplier or catalog; and receiving a userrequest to associate a specific item attribute to the contract.

In yet another aspect, a computer-implemented method includes the stepsof, at a server system hosting an electronic procurement system:receiving a user request for access to the system; granting access to auser; receiving a user request to add a item to a shopping cart; andassociating the item to a contract.

In yet another aspect, a computer-implemented method includes the stepsof, at a client system communicating with an electronic procurementsystem: sending a user request for access to the system; receivingaccess to the system; sending a user request to access or create acontract between a user organization and a supplier or catalog; andsending a user request to associate a specific item attribute to thecontract.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory and areintended to provide further explanation of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of the specification, illustrate embodiments of the invention andtogether with the description serve to explain the principles of theinvention. In the drawings:

FIG. 1 is a block diagram illustrating an exemplary embodiment of aneProcurement system in accordance with the present invention;

FIG. 2 illustrates an exemplary embodiment of an eProcurementarchitecture in accordance with the present invention;

FIG. 3 illustrates an exemplary user interface in accordance with thepresent invention;

FIGS. 4A-4T illustrate exemplary user management tools in accordancewith the present invention;

FIG. 5A illustrates an exemplary user setting tool in accordance withthe present invention;

FIG. 5B illustrates an exemplary roles selection tool in accordance withthe present invention;

FIG. 5C illustrates an exemplary email preference tool in accordancewith the present invention;

FIG. 5D illustrates an exemplary navigation setup tool in accordancewith the present invention;

FIG. 5E illustrates an exemplary user purchasing tool in accordance withthe present invention;

FIG. 5F illustrates an exemplary punch-out access tool in accordancewith the present invention;

FIGS. 5G-5M illustrate exemplary user permission tools in accordancewith the present invention;

FIGS. 5N-5O illustrate exemplary materials management tools inaccordance with the present invention;

FIGS. 6A-6J illustrate exemplary organization setup tools in accordancewith the present invention;

FIG. 7 illustrates an exemplary workflow setup tool in accordance withthe present invention;

FIGS. 8A-8D illustrate exemplary search engines in accordance with thepresent invention;

FIGS. 9A-9F illustrate exemplary catalog management tools in accordancewith the present invention;

FIG. 10 illustrates an exemplary contracts management tool in accordancewith the present invention;

FIGS. 11A-D illustrates an exemplary cart and requisition tool inaccordance with the present invention;

FIG. 12 illustrates an exemplary workflow setup tool in accordance withthe present invention;

FIG. 13 illustrates an exemplary purchase order approval tool inaccordance with the present invention;

FIG. 14 illustrates an exemplary history tool in accordance with thepresent invention;

FIG. 15 illustrates the electronic procurement system communicating overa network with suppliers and purchasing organizations;

FIG. 16 illustrates the purchasing organization client communicatingover a network with the purchaser server application to access theengines of the purchaser server application;

FIG. 17 illustrates the supplier client communicating over a networkwith the supplier server application to access the engines of thesupplier server application;

FIG. 18 illustrates the features and database accessible via thesupplier client;

FIG. 19 illustrates the features and database accessible via thepurchasing organization client;

FIG. 20 illustrates a server system hosting an electronic procurementsystem running on the server;

FIG. 21 illustrates a client system providing access to an electronicprocurement system running on a server;

FIG. 22 illustrates a top-level data structure for electronicprocurement system;

FIG. 23 illustrates a data structure for a master database, showingcontents of a forms database;

FIG. 24 illustrates a data structure for a master database, showingcontents of a catalog database and search database for indexing themaster database;

FIG. 25 illustrates a data structure for a transaction database, showingcontents of a purchase order database;

FIG. 26 illustrates a data structure for a transaction database, showingcontents of a fax, distribution and revisions databases;

FIG. 27 illustrates a data structure for a transaction database, showingcontents of a requisition database;

FIG. 28 illustrates a data structure for a transaction database, showingcontents of a receipt database;

FIG. 29 illustrates a data structure for a transaction database, showingcontents of a sales order database;

FIG. 30 illustrates a data structure for a transaction database, showingcontents of a workflow database;

FIG. 31 illustrates a data structure for a staging database, showingcontents of a staging catalog database;

FIG. 32 illustrates a data structure for a transaction database, showingcontents of a contracts database;

FIG. 33 illustrates a data structure for a transaction database, showingcontents of a buyer invoice database;

FIG. 34 illustrates a data structure for a transaction database, showingcontents of a seller invoice database;

FIG. 35 illustrates a data structure for an end user database, showingcontents of a user/security database;

FIG. 36 illustrates a data structure for a scheduler database, showingcontents of the scheduler database;

FIG. 37 illustrates an exemplary new/non-catalog item administrativesetup tool in accordance with the present invention;

FIG. 38 illustrates an exemplary new/non-catalog item access tool inaccordance with the present invention;

FIG. 39 illustrates an exemplary new/non-catalog item creation tool inaccordance with the present invention;

FIG. 40 illustrates an exemplary form layout configuration tool inaccordance with the present invention;

FIG. 40A illustrates an exemplary form general configuration tool inaccordance with the present invention;

FIG. 41 illustrates an exemplary form user interface in accordance withthe present invention;

FIG. 42 illustrates an exemplary form library interface in accordancewith the present invention;

FIG. 43 illustrates an exemplary forms search results interface inaccordance with the present invention;

FIG. 44 illustrates an exemplary user-defined searchable attributesconfiguration interface in accordance with the present invention;

FIG. 45 illustrates an exemplary user-defined searchable attributes itemassignment interface in accordance with the present invention;

FIG. 46 illustrates an exemplary search interface with user-definedsearchable attributes in accordance with the present invention;

FIG. 47 illustrates an exemplary contract general setup interface inaccordance with the present invention;

FIG. 48 illustrates an exemplary contract details setup interface inaccordance with the present invention;

FIG. 49 illustrates an exemplary purchase order-to-contract associationinterface in accordance with the present invention;

FIG. 50 illustrates an exemplary forms-to-contract association interfacein accordance with the present invention;

FIG. 51 illustrates an exemplary contract owners interface in accordancewith the present invention;

FIG. 52 illustrates an exemplary contract budget interface in accordancewith the present invention;

FIG. 53 illustrates an exemplary contract user criteria interface inaccordance with the present invention;

FIG. 54 illustrates an exemplary contract other criteria interface inaccordance with the present invention;

FIG. 55 illustrates an exemplary contract history interface inaccordance with the present invention;

FIG. 56 illustrates an exemplary contract price sets interface inaccordance with the present invention;

FIG. 57 illustrates an exemplary contract search interface in accordancewith the present invention;

FIG. 58 illustrates an exemplary contract view interface in accordancewith the present invention;

FIG. 59 illustrates an exemplary contract pricing interface inaccordance with the present invention;

FIG. 60 illustrates an exemplary contract search interface in accordancewith the present invention;

FIG. 61 is a flowchart representing a server method for SKU basedcontract management;

FIG. 61A is a flowchart representing a server method for shopping cartand price validation features of SKU based contract management;

FIG. 62 is a flowchart representing a client method for SKU basedcontract management;

FIG. 63 illustrates an exemplary add products to contract interface inaccordance with the present invention;

FIG. 64 illustrates an exemplary auto look-up catalog items interface inaccordance with the present invention;

FIG. 65 illustrates an exemplary add/remove multiple products to/fromcontract interface in accordance with the present invention;

FIG. 66 illustrates an exemplary search and display assigned productsinterface in accordance with the present invention;

FIG. 67 illustrates an exemplary remove assigned products interface inaccordance with the present invention;

FIG. 68 illustrates an exemplary validate and import products interfacein accordance with the present invention;

FIG. 69 illustrates an exemplary export assigned products interface inaccordance with the present invention;

FIG. 70 illustrates an exemplary field management interface inaccordance with the present invention;

FIG. 71 illustrates an exemplary update favorite(s) process flow inaccordance with the present invention;

FIG. 72 illustrates an exemplary document attachment and setup interfacein accordance with the present invention;

FIG. 73 illustrates an electronic procurement system hosted at asupplier server; and

FIG. 74 illustrates an electronic procurement system hosted at apurchaser server.

DETAILED DESCRIPTION

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous non-limiting specific details are set forth inorder to assist in understanding the subject matter presented herein. Itwill be apparent, however, to one of ordinary skill in the art thatvarious alternatives may be used without departing from the scope of thepresent invention and the subject matter may be practiced without thesespecific details. For example, it will be apparent to one of ordinaryskill in the art that the subject matter presented herein can beimplemented on any type of client-server compatible system containingany type of client, network, server, and database elements.

The terms module, engine, and application are used interchangeablyherein.

FIG. 1 is a block diagram illustrating an exemplary embodiment of aneProcurement system in accordance with the present invention. The term“eProcurement architecture” used herein refers to a system and methodthat facilitates customized searching, data modeling, and orderprocessing over an electronic network, using a client-server typearchitecture, where multi-tenants (e.g., end users/consumers, supplierusers, etc.) can realize each of their specific business requirementswith respect to the process of initiating and consummating transactions.In general, the eProcurement architecture of the present inventionfacilitates transactions between end users and suppliers. The end usersmay be individual users or members of an organization, such as a companyor institution. For example, the end users may be any member of theorganization authorized for performing procurement operations for theorganization or the end user may be an individual of a soleproprietorship.

In a multi-person organization, procurement operations of theorganization are setup in a multi-level structure with a group ofindividuals who make requests for requisitions and an authorizing entity(e.g., manager) who approve such requests based on the organization'sprocurement policies. There may be a plurality of individuals assignedas the authorizing entity, and the authorizing entity may itself includemultiple levels of authority with each higher level having more controlover the procurement operations. The procurement policies may define thelevels of authority, such as who can order what, and include one or morecontractual relationships between the organization and one or moresuppliers. By way of example only, the procurement policy may definethat the lowest level end user of a particular department can only ordercertain products or services while a higher level end user can order orauthorize orders of broader categories of products and/or services. Inanother example, the procurement policy may require that certainproducts or services be ordered exclusively from a supplier with anexclusive contract with the organization. As another example, theprocurement policy may require that a particular product be ordered in apredetermined lot size due to a contractual discount negotiated from aparticular supplier. The eProcurement architecture of the presentinvention facilitates transactions between multiple end users of anylevel of any organization with multiple suppliers taking into accountthe procurement policies associated with each end user and supplier on asingle platform (i.e., single instance, multi-tenant architecture).

As shown in FIG. 1, the eProcurement system 10 of the present inventionincludes end users 12, supplier users 14, and the procurement module 20connected over a data communications network 16. The procurement module20 includes access module 21, search engine 22, transaction module 23,business rules engine 24, and data repository 30. The data repository 30may include one or more databases to store user data 32, hosted productindex 34, product data 36, and transaction data 38.

The access module 21 allows the end users and suppliers to set up andgain access to their respective accounts in the eProcurement system 10.For example, the access module 21 may include registration/account setupprocedures to create a new account on the eProcurement system 10. Theaccess module 21 may also include authentication procedures (e.g., loginID and password) to determine the identity of the user and the user'sprofile (e.g., associated organization, level of access, etc.) beforegranting access to the procurement module 20. Once granted access, theuser may configure the account for customized access. If the user is a“super user” (i.e., a user with higher levels of access, such as aprocurement supervisor of an organization), the super user may setconditions for access of other users from his organization. If the useris a supplier, the supplier user may create or update the supplieraccount or provide/update product/service information (e.g., productcatalog).

The search engine 22 allows the user to search through the hostedproduct index 34 to find a product and/or service provided by the one ormore suppliers. In general, the search engine 22 searches through thehosted product index 34, which contains tokenized data of all theproducts from all the suppliers stored in the product database 36. Thesearch results of the search are processed by the business rules engine24 and displayed to the user based on the business rules set for theuser and the user's organization. The search engine 22 includes apunch-out module 22 a that allows the user to “punch-out” to an unhostedsupplier catalog for products/services not available through theeProcurement system 10. The user can only access those punch-outsuppliers configured for him/her according to the business rules engine24.

The transaction module 23 includes one or more of requisition module 23a, order module 23 b, and tracking module 23 c to facilitate atransaction with one or more suppliers. The requisition module 23 aprocesses items selected by the user from the search engine 22 andcreates a requisition. If authorization is required, the requisitionmodule 23 a notifies the designated authorizing entity of therequisition to obtain authorization. If the requisition is denied, therequisition module 23 a sends a notification back to the user of thedecision. If the requisition is approved, the user is notified and therequisition either a) is sent to order module 23 b, or b) is marked as“complete” based on the business rules engine 24 because not allrequisitions are necessarily converted to orders. The order module 23 bconverts the requisition into a purchase order according to the businessrules in the business rules engine 24. The order module 23 b sends thepurchase order to the appropriate supplier in the proper format(s)designated for that supplier. Once the purchase order has been sent, thetracking module 23 receives confirmation of the purchase orders from thesuppliers and keeps track of the purchase orders through the fulfillmentprocess.

In general, a user (i.e., end user, super user, supplier user, etc.)gains access to the procurement module 20 through the access module 21.The access module 21 may include security measures, such asauthentication (e.g., providing user ID and password), to identify theuser by accessing the user data stored in the user database 32. Useraccounts may also be created through the access module 21. For example,a user (generally a super user) creates an account on the eProcurementsystem 10 by registering through the access module 21. The account mayalso be created by a system administrator of the eProcurement system 10off-line who gives access to the user via emailing a registration linkto the access module 21. Once an account has been created, the user mayaccess the eProcurement system 10 through the access module 21.

FIG. 2 illustrates an exemplary embodiment of an eProcurementarchitecture in accordance with the present invention. As shown in FIG.2, the eProcurement architecture of the present invention may includeone or more end user/consumer interfaces 212 and supplier userinterfaces 214, which may connect to one or more servers 220 over awired or wireless network 216. These one or more servers 220 may be foruser processing (e.g., end user processing servers 221), productdatabase hosting (e.g., custom database servers 222), transactionprocessing (e.g., transaction processing servers 223), middleware/webmethods (e.g., middleware/web methods servers (e.g., business rules)224—e.g., for implementing business rules between end users and supplierusers), and communication processing (e.g., web servers 225), such asstreaming data/media, file hosting (e.g., FTP—File TransferProtocol—server), web serving (e.g., HTTP/HTTPS, WWW, CGI—Common GatewayInterface, ASP—Active Server Pages, Servlets, JSP—Java Server Pages,etc.), facsimile transmission, proxy, telnet, chat, list, mail (e.g.,SMTP—Simple Mail Transfer Protocol), news (e.g., NNTP—Network NewsTransfer Protocol), groupware, and other communication/data processingpurposes. These one or more servers 220 may be hosted behind or outsidea firewall 218 with or without failover and/or load balancers. These oneor more servers 220 may be hosted over the Internet, within the sameIntranet and/or subnet, on different Intranets and/or subnets, or in anyother inter-networked configuration of network 216. The servers 220 maybe implemented on Microsoft™ Windows NT/2000/XP™/XPProfessional/Server™/Vista™ (e.g., Microsoft™ Internet InformationServices (IIS)), Apache, Unix™, z/OS™, z/VM™, Linux™, VMS, NetscapeEnterprise Server™, iPlanet™ Web Server, Sun Java System Web Server,Oracle™ Server, SQL Server™ (e.g., Microsoft™, Sybase™, MySQL™ etc.),Terradata server applications, or any other compatible servertechnology.

End user interfaces 212 and supplier user interfaces 214 may beimplemented on Internet web browsers such as Microsoft InternetExplorer™, Netscape Navigator™, Mozilla™ Firefox™, Opera, Satori,Blazer, or any other Internet web browser capable of sending andreceiving data using the Hypertext Transfer Protocol (HTTP). The datamay be transferred over an encrypted and authenticated communicationlayer (i.e., using secure HTTP, or as more commonly known, HTTPS). Enduser interfaces 212 and supplier user interfaces 214 may be implementedusing a combination of HTML (Hypertext Markup Language), MacromediaFlash™, XML (Extensible Markup Language), CGI (Client GatewayInterface), ASP (Active Server Pages), JSP™ (JavaServer Pages), PHP(Hypertext Preprocessor), Java, C/C++, Visual Basic™, Visual BasicScript, Perl™, Tcl/Tk, SQL (Structured Query Language), and any otherrelevant markup/programming/scripting/query language or developmentenvironment.

Communication from the end user interfaces 212 and supplier userinterfaces 214 to the server or plurality of servers 220, via thefirewall 218 with failover and load balancer, may be implemented overwired communication protocols through network 216. For example, at theWide Area Network (WAN) level or at the Local Area Network (LAN) level,routed Internet Protocol (IP) packets may be transported using the IEEE802.3 Ethernet standard, for example, on the data link network layer.However, any network standard may be used, whether for packetencapsulation, path determination and logical addressing, or physicaladdressing, at any layer of these layers without departing from thescope of the invention. Also, the packet data may be transported overinterconnected hubs (not shown), switches 226, routers 227, and othernetwork elements. At the WAN level, protocols such as Packet overSynchronous Optical Network (SONET) or Synchronous Digital Hierarchy(SDH), Asynchronous Transfer Mode (ATM) over SONET, Multi-protocol LabelSwitching (MPLS), packet over Frame Relay, or other analogous protocolsmay be used to deliver data over longer distances. Interconnectrepeaters, multiplexers (e.g., add/drop), and cross connects may be usedto facilitate and ensure accurate transmission over the long-haul frompoint-to-point.

Communication from the end user interface 212 and supplier userinterfaces 214 to the server or plurality of servers 220, via thefirewall 218 with failover and load balancer, may also be implementedover wireless communication protocols over network 216. For example, atthe LAN level (i.e., WiFi), standards such as 802.11a, 802.11b, 802.11g,and 802.11n may be used to deliver data from point-to-point. Similarly,at the Metropolitan Area Network (MAN)/WAN level, standards such as802.16e (i.e., WirelessMAN), WiMax, Universal Mobile TelecommunicationsSystem (UMTS) over Wideband Code Division Multiple Access (W-CDMA), GSM,GPRS, or EDGE may also be used to deliver data from point-to-point. Aswith the wired networks, other standards and protocols may be usedwithout departing from the scope of the invention.

The eProcurement architecture of the present invention includes a datarepository 230. The data repository 230 may be implemented using one ormore databases to store end user data 232, hosted product index 234,master product data 236, and transaction data 238, in accordance withbusiness rules (implemented via, for example, a business rules engine24). The data repository 230 may be implemented using any type of datastorage device without departing from the scope of the presentinvention. Moreover, the data repository 230 may be managed by anydatabase platform (e.g., Oracle, Microsoft Access, IBM DB2, etc.)without departing from the scope of the present invention.

End user interfaces 212 and supplier user interfaces 214 may also allowan implemented feature that enables the setting of user configurationpreferences. This feature allows a super user, with enhancedadministrative capabilities, to have full access to the features of enduser and supplier user interfaces. Some of these features may include:sending an email notification of a specific requisition order, and acorresponding link for accessing the same; full access to the featuresof the end user and supplier user interfaces; the capability to approveor reject a full order or a specific order item requested by an enduser; the capability to take ownership and/or control of a specificrequisition order, which may be organized according to a product orsupplier category; the capability to expedite or accelerate an orderthrough to specific steps along the ordering process, including thefinal review step; and, the capability to invoke and view a summary andhistory of each end user's latest order activity.

Moreover, a super user, for example, may design and/or otherwiseconfigure and customize the style, type, layout, and level of data thatis displayed on the respective end user interface 212 and supplierinterface 214 for their respective organizations. A super user is alsoable to invoke a setup feature to choose which end users may have accessto specific suppliers. Furthermore, a super user may also determine whatinformation is required from the end users and supplier users of theirrespective organization, and determine the level of access at which anend user may access a specific supplier within the hosted supplierproducts catalog. This capability enables a super user to configure, forexample, whether an end user can view specific products from specificsuppliers, the currencies given for product/item pricing, and placeorders. Moreover, the end user interface of the present invention allowsfor features of the present invention to be configured as permissiondriven. As such, certain features may be accessible to each end user,based on the end user's precedence within the organization, which likelyaffects his/her corresponding permission level. In addition, eachfeature is configurable to each end user based on a set of variableoptions. These variable options may include the ability to set aspecific layout/view, a preferred number of search results, a preferredlist of products, or a preferred list of suppliers. Also, each featuremay include a help function that allows an end user to resolve inquiriesor difficulties relating to the feature. The end user interfaceimplementation is usually account login-based and, as described infurther detail above, may encompass multiple server types (e.g., runninga Linux OS), a redundant firewall and load balancer, and apriority-based software programming architecture (e.g., implemented inJAVA and JSP).

FIG. 3 illustrates an exemplary user interface in accordance with thepresent invention. For purposes of example only, an end user interfaceis used to describe various aspects of the present invention. As shownin FIG. 3, user interface 300 provides customized information for theuser. For example, the user is a member of a fictitious group named WeetOrganization. The user interface 300 includes one or more of anorganizational message area 310, any system message area 320, and taskitems area 330. In the example shown, the user is a super user andtherefore, the “Admin” tab 340 is active. Had the user been an end user,the “User” tab would be active and the “Admin” tab 340 either would notbe displayed or would be inactive. All of these areas and informationdisplayed therein may be customized through the access module 21. Anyconfiguration definitions are then stored in the user database 32 andinvoked upon access/login.

FIG. 3 illustrates an exemplary embodiment of the configuration toolsavailable to a super user. In general, the eProcurement system 10 of thepresent invention provides a super user the tools needed to configureevery aspect of the eProcurement process of an organization for completecustomization, thereby effectuating a single instance multi-tenantarchitecture. That is, the eProcurement system 10 establishes acentralized system that is customizable for each user and/ororganization, thereby providing a robust and yet an efficienteProcurement system. More specifically, configuration tool 350 allows asuper user to customize the configuration of the eProcurement system 10specifically for an organization and its users. While exemplaryconfiguration tools are shown, other tools may be included withoutdeparting from the scope of the present invention.

FIG. 4A illustrates an exemplary user management tool 400 to create ormodify user access, manage user registration, and define theorganizational structure. For example, FIG. 4A illustrates a user accesshuman resources (HR) configuration tool 440. In particular, HRconfiguration tool 440 allows the super user to establish and describethe organization. For example, the HR configuration tool 440 may be usedto define various departments of the organization (442), variouspositions of the organization (444), various roles of the users in theorganization (446), and relationships between the roles, positions, anddepartments defined for the organization (448). As shown in FIG. 4A, thevarious departments of the organization that require procurementservices may be “Engineering,” “IT,” “Legal,” “Math,” etc. As shown inFIG. 4B, there may be various positions within the organization, such as“Buyer,” “Documentation Editor,” “Professor, “Researcher,” etc. As shownin FIG. 4C, the HR configuration tool 440 is used to define variousroles of the users within the organization, such as “Administrator,”“Approver,” “Catalog Manager,” etc. As shown in FIG. 4D, the HRconfiguration tool 440 is used to define the relationship between thedepartment, position, and role of the users. For example, a “Professor”in “Engineering” may be designated as an “Approver” and “Requisitioner”for the organization while a “Researcher” of “Engineering” may only be a“Requisitioner.” In this manner, the HR configuration tool 440 providesa simple yet efficient mechanism to define the organization for whichthe eProcurement system 10 is to be utilized.

Once the organization has been defined through the HR configuration tool440, user access tool 410 may be used to create or modify a user'saccess to the eProcurement system 10 for the user's organization. Asshown in FIG. 4E, the user access tool 410 may be used to create a newuser access account (410 a) or the user database 32 may be searched (410b) for an existing user in the eProcurement system 10. To create a useraccess account, the user access tool 410 requires entry of the user'spersonal information (e.g., name, phone number(s), email address) andauthentication information (e.g., login ID and password). In addition,the user's department and position information as created through the HRconfiguration tool 440 is also provided. In an exemplary embodiment, thedepartment and position information created through the HR configurationtool 440 are shown in a drop-down menu for easy selection and entry. Tosimplify the creation of an account, existing user files may be importedinto the user database through the user import 430. Once a user accessaccount has been created, the newly created accounts are activatedthrough the user registration monitor 420. As shown in FIG. 4F, a listof new user access requests is presented in the user registrationmonitor 420. A designated approver for the organization then reviews andapproves the user access account to be activated for the user.

In accordance with an exemplary embodiment of the present invention,every aspect of the organization may be defined and customized in theeProcurement system 10. For example, as shown in FIG. 4A, once a“Department” has been created for an organization, the createddepartment may be activated (442 a). Moreover, each department may bedefined with business rules related to the department's requisition (442b), purchase orders (442 c), and fulfillment (442 d). For example, FIG.4A shows that the “Engineering” department has been designated as anactive department with the “Requisition” and “Purchase Order” rulesincluding a list of approvers for the Engineering department. As shownin FIG. 4B, a created position may be designated for a createddepartment. For example, FIG. 4B shows that the organization has the“Professor” position for the “Engineering,” “Math,” “Microbiology,” and“Purchasing” departments. FIG. 4G illustrates an exemplary embodiment ofthe HR configuration tool 440 for defining roles of the organization.

For each role, the roles configuration tool 446 is used to define therole properties (446 a), purchasing properties (446 b), accesspermissions (446 c), materials management rules (446 d), and history ofmodifications to these definitions (446 e). For example, for the role of“Administrator,” the role properties 446 a (FIG. 4G) may include whetherthe designated role is active in the organization and the purchasingproperties 446 b may include definitions of any internal and externalpurchasing codes and information (e.g., “PRWF”) (FIG. 4H),purchasing/approval limits (FIG. 4I), allowed product views (FIG. 4J),and allowed punch-out access (FIG. 4K). The access permissions 446 c maybe defined for the roles including shopping cart permissions (FIG. 4L),orders (FIG. 4M), approvals (FIG. 4N), accounts payable (FIG. 4O),administration (FIG. 4P), management of materials (FIG. 4Q), and customfields permissions (FIG. 4R). The materials management 446 d defines theavailable projects and location of groups to the various roles (FIG.4S). The history section 446 e keeps track of a history of all theactions (e.g., modified, created, product view added, product viewremoved, punch-out access added, punch-out access removed, projectadded, project removed, location added, location removed, etc.) and thesections to which the actions were applied (e.g., role properties,product views, punch-out access, materials management, permissions,purchasing/approval limits, custom field permission definitions, etc.)including the old value of the parameter and the new value of theparameter (FIG. 4T).

Once the internal organizational structure and descriptions of keypositions of users in the organization have been defined using the usermanagement tool 400, specific users and their level of access may bedefined. As discussed above, the level of access of a user may beassigned globally based on their positions and/or roles in theorganization. In addition, the eProcurement architecture of the presentinvention allows customization down to specific individuals all withinthe single instance, multi-tenant environment. For example, FIG. 5Aillustrates an exemplary user profile tool 500 for defining a user'saccount in the eProcurement system of the present invention. As shown,the user profile tool 500 includes one or more of a user setting tool510, user purchasing tool 520, user permissions tool 530, user materialsmanagement tool 540, and user setting history tool 550. These toolsprovide customization of the user's account for various levels of accessto the eProcurement system of the present invention all within thesingle instance, multi-tenant environment.

For example, as shown in FIG. 5A, an exemplary user setting tool 510 ofthe present invention shows that the user is a “Professor” in the“Engineering” department. As discussed above, users in this departmentand position have default levels of access defined by a super user usingthe user management tool 400. However, because a user may haveadditional roles assigned to the user that are beyond the normal scopeof the user's position, the eProcurement system of the present inventionallows a super user to modify the user's level of access on anindividual level. For example, FIG. 5B illustrates an exemplary rolesselection tool 510 c to modify the roles assigned to the selected user.Through the roles selection tool 510 c, a super user may be able tospecifically tailor the roles of a user down to the individual level toprovide customized access to the eProcurement system of the presentinvention. Similarly, the user's departmental permissions may bemodified using the department permissions tool 510 d. Various aspects ofthe user's account may also be customized, such as the user's personalsettings 510 b, email preferences 510 e, and navigation setup 510 f. Aswith the user management tool 400 and the roles/permissions tools 510 cand 510 d, all customizations may be performed by simplyactivating/deactivating a function available on the eProcurement systemof the present invention. For example, FIG. 5C illustrates an exemplaryemail preference tool 510 e, which lists all of the action notificationsthat may be received via email. A user only has to activate/deactivate apreference by selecting the notifications the user wishes to receive viaemail. Similarly, FIG. 5D illustrates an exemplary navigation setup tool510 f. As shown, a user simply selects the navigation tools to bedisplayed (or removed) from the top-level navigation bar.

The user purchasing tool 520 shown in FIG. 5E allows a super user todefine the purchasing activities of the user. For example, as shown inFIG. 5E, user purchasing tool 520 includes one or more of the customfields tool 520 a, financial approvers tool 520 b, purchasing/approvallimits tool 520 c, shipping/billing address tool 520 d, product viewstool 520 e, and punch-out access tool 520 f. The custom fields tool 520a is similar to the purchasing properties tool 446 b (FIG. 4H) to definethe internal and external codes needed to make a purchase (e.g., productcode). The financial approvers tool 520 b designates purchase approversfor the user. Default, preferred, and additional approvers may bedesignated through the financial approvers tool 520 b as well asremoving approvers for the user. The purchasing/approval limits tool 520c designates the limits of purchases and/or approvals of purchasesallowed for the user. FIG. 5E illustrates an exemplary view of thepurchasing/approval limits tool 520 c. As shown, the limit values ofvarious activities related to purchases may be defined for the user. Theshipping/billing address tool 520 d designates the shipping/billingaddress associated with the user. The product views tool 520 edesignates the type of products the user is allowed to view. Thepunch-out access tool 520 f designates the punch-out catalogs that areallowed to be accessed by the user. For example, FIG. 5F illustrates anexemplary punch-out access tool 520 f. As discussed above, thesesettings may be designated as a default based on thedepartment/position/role assigned to the user. However, these tools maybe used to customize the default settings for the specific individualuser in accordance with the present invention.

In a similar fashion, the user permissions tool 530 includes one or moreof tools to customize the user's access to the shopping cart (FIG. 5G),order processing (FIG. 5H), approval processing (FIG. 5I), accountspayable processing (FIG. 5J), administration permissions (FIG. 5K),materials management (FIG. 5L), and custom fields permissions (FIG. 5M).The materials management tool 540 designates inventory locations basedon projects and groups (FIG. 5N) as well as default/preferred accesslocations (FIG. 5O). As discussed above, the history tool 550 keepstrack of all actions/changes made to the various parameters.

FIG. 6A illustrates an exemplary organization setup tool 600 fordesignating business rules such as method of payment (FIG. 6A), tax(FIG. 6B), shipping/handling (FIG. 6C), settlement (FIG. 6D), purchaseorder terms (FIGS. 6E-G), order distribution process (FIGS. 6I-J), andhistory of all actions effectuated through the organization setup tool.By organizing all of the terms and conditions of an order for eachorganization in a single instance, multi-tenant architecture, eachrequisition effectuated on the eProcurement system of the presentinvention is processed efficiently.

FIG. 7 illustrates an exemplary workflow setup tool 700 to define theworkflow process of a requisition, purchase order, and fulfillment. Asshown in FIG. 7, the workflow setup tool 700 in accordance with thepresent invention creates a shared workflow space 710 and allows for theassignment of users (e.g., individual users, or users of various userroles) to be included in the workflow process.

Other configuration tools include document attachment and setup tool(FIG. 72, document attachment and setup interface) to organize documentsrelated to requisitions, purchase orders, and sales orders for access bythe user. The document attachment and setup tool keeps track of the nameof the document creator, version number, and any deployment dates, aswell as other data related to the document. Moreover, the eProcurementsystem in accordance with the present invention includes a fieldmanagement tool (FIG. 70, exemplary field management interface) thatallows super users to create, modify, and manage every field/parameterrelated to the procurement process used on the system. Accordingly, theeProcurement system of the present invention may be custom tailored foreach organization/user role/user while maintaining its single instance,multi-tenant environment.

As shown in FIG. 2, end user interfaces 212 and supplier user interfaces214 according to the present invention provide access to the pluralityof modules of the eProcurement system 10 (FIG. 1). As described above,the end user interface 212 is configurable by both end user and superusers. Moreover, the end user interface 212 includes one or morefeatures, for example, such as searching and viewing a hosted supplierproducts catalog, invoking purchase/requisition orders, consummatingsales transactions, invoking status queries and viewing the response,and setting end user configuration preferences as described furtherbelow. For example, the search and view feature allows for searching viaproduct description, supplier name, manufacturer name, catalog no.(SKU), a filtering capability, and by browsing: catalog/non-catalogitems, suppliers, or contracts. A user may invoke any of these searchinputs alone or in combination with others. Also, Boolean and fuzzylogic functionality is available for searching and allows a user todevise targeted search strategies that may return more accurate searchresults. Once a user has invoked a search using any of the inputsdescribed, the user may then view the returned results. The returnedresults can be filtered by a user based on category or supplier. Also, auser may choose to organize the returned results such that similarresults are listed in proximity of one another. For example, a user mayorganize returned results by weight, supplier, category, catalog number,product description, UOM, product size, price, quantity, and/orcurrency.

The catalog may be implemented as single instance but multi-tenant (or,as multiple instance, single-tenant), and may further include customviews of items as set by each internal end user and/or organization. Anend user may specify favorites within the catalog. Such favorites areavailable for later viewing or purchasing by the end user. Any updatesmade to an end user favorite within the catalog will be automaticallypropagated to the end user's favorite(s) view as well (FIG. 71, anexemplary update favorite(s) process flow). The catalog may allow forsupplier classifications and multiple products may be linked to a singlesupplier. Also, the catalog can be activated or deactivated through asimple click on the end user interface, and specific product categoriescan be globally manipulated and applied to affect all end users. Eachcatalog may contain information regarding one or more suppliers, and amaster product database is primarily tasked with populating each hostedsupplier products catalog. This master product database is a relativelylarge database with a plurality of attributes related to one or morespecific products.

In addition to the hosted supplier products catalog, punch-out catalogsmay also be implemented as an alternative and supplement to the hostedsupplier products catalog, and are made available, for example, when thehosted supplier products catalog does not yield sufficient orsatisfactory results. The punch-out catalogs link to outside/third-partycatalogs, are not hosted, and may also contain end userorganization-specific prices. Processing modules executed on the customdatabase servers invoke each punch-out instance. Multiple punch-outcatalogs may be accessible by a single end user. An end user can returnfrom a punch-out catalog to the hosted supplier products catalog, andthe remainder of the features of the eProcurement architecture, via asubmit feature, which will then return to the processing module thatinitially invoked the punch-out instance. Punch-out catalogs may beconfigured to display relevant catalogs to an end user, based on the enduser organization. An end user can browse punch-out catalogs to searchfor more accurate results and may, subsequently, invoke a requisitionorder via the third-party web site and order processing methods. Also,one or more purchase orders can be sent from one or more punch-outcatalogs, but each punch-out order session may generate a singlepurchase order that may ultimately include orders from non-punch-out orhosted catalogs.

Further, with respect to the hosted supplier products catalog, there maybe a feature implemented to allow both its searching and viewing. Thesearch/view catalog feature is invoked via a processing module thatexecutes on the custom database servers. Upon the execution of such asearch by an end user, search results can be displayed via the end userinterface. The catalog search results can be displayed, for example,using a static or dynamic interactive list or table, attachment,graphic, or link. An end user may also have the option of choosing theappropriate supplier(s) from which to place an order. Upon an end user'sselection of a particular supplier, the relevant supplier data is thenforwarded to the transaction processing feature. The end user may laterinvoke a status query, via a processing module executed on the customdatabase servers, on a preexisting order and, subsequently, receivestatus notifications regarding the order.

The search feature may be implemented using several sub-features suchas, for example, customized annotations (with icons) ofpreferred/contract suppliers, a product/supplier filter, and a productsize filter. The search feature is invoked by a processing module thatis executed on the custom database servers. The customized annotations(with icons) of preferred/contract suppliers allows certain products tobe highlighted within search results. Furthermore, the product/supplierfilter of the search feature allows certain products to be displayed,while others are hidden, depending on specific filter criteria chosen bythe end user/organization. Such criteria may include, for example, pricethresholds, hazard level, approximate delivery date, product size,supplier, and/or currency.

The search architecture is based upon an indexed, tokenized-typeimplementation. This search architecture may include a search engine anda tokenization feature, both of which are invoked via processing modulesexecuted on the custom database servers. Product elements such as theproduct name, industry, price, currency, and availability, among others,are primarily used to generate a product search index (e.g., a token).The process of generating a product search index/token is called“tokenization” and may be executed by a tokenization feature invoked viaa processing module. The indices/tokens generated as a result of thetokenization feature, which relate to various products of a multitude ofsuppliers, may be stored within and executed on the hosted supplierproducts catalog. Searching is executed against “verticals.” A verticalis designed similar to a drill-down menu architecture that consists ofroot nodes and leaf nodes, which are children of their respective roots.Through the use of tokenization and verticals, a layer of abstraction isadded that is unique in comparison to typical text-based searching of alarge database, like the master product database. This added layer ofabstraction allows for better organization of the underlying data. As aconsequence, the use of tokens to search verticals, which organizesupplier product data and search the hosted supplier products catalog,enables an efficient and methodical search strategy to be executed.Search results returned from searching the hosted supplier productscatalog are forwarded back to the search engine and may appear via theend user or supplier user interfaces. For an end user, designatedpreferred suppliers usually appear first in the search results.

Further contained within the search architecture, a feature to allow theinvocation of status queries and viewing of the response may beimplemented. This feature allows a plurality of end users to sendqueries/requests via middleware/web methods, or direct Internet postingtechniques, to the product catalog. The feature is itself invoked by aprocessing module that executes on the custom database servers. Suchqueries/requests may be intended for finding, buying, or managingproducts. Such products may be those of preferred contractors that arematched to the end user based on a plurality of criteria likepermission, product type, industry, price, quality control metrics,delivery date, warranty types, currency, and/or locale. Each productcatalog may contain information regarding one or more specific products.A master product database populates the hosted supplier products catalogwith various types of information relating to one or more specificproducts. The various types of information may include a “stock keepingunit” (SKU) identifier, supplier information, and productcategory/description/attribute information.

Further also to the search architecture, an in-stock query feature maybe implemented to allow an end user, through the middleware/web methods,or direct Internet posting techniques, to determine whether any suppliermight have a particular product in-stock, and/or the warehouse/locationwhere that stock is maintained. The feature is itself invoked by aprocessing module that executes on the custom database servers. Once thein-stock query feature is invoked, relevant suppliers are sentindividual queries. Subsequently, each supplier response to an in-stockquery is processed and the appropriate end user is notified after thein-stock query receives the supplier response(s), but before returningto the processing module.

Moreover, a quick order feature may also be implemented to enableseveral other sub-features such as, for example, searching by productcategory, SKU identifier, currency, or host product categorynumber/supplier part number. The feature is itself invoked by aprocessing module that executes on the custom database servers.Subsequently, the order feature is initially invoked by an end user thathas completed a quick order search. Thus, the quick order featureenables an end user that may have knowledge of specific productattributes to perform an expedited search, retrieve search results, andproceed to ordering.

The search results of a product search exhibit other features of theinvention such as those related to the presentation of results. Forexample, suppliers and categories contained within search results can bedisplayed using different customizable icons, which may be used tohighlight specific suppliers and product categories. Such results canalso be ranked according to priority based on whether they are suppliedfrom preferred or contracted suppliers, a preferred category of productsfrom suppliers, or a preferred currency. Non-preferred or non-contractedsupplier or currency results may also presented to end users. Moreover,a product comparison chart can be invoked to highlight the differencesand similarities among two or more products. The chart can containstatic or dynamic presentation attributes based in part onsupplier-provided data. For example, the in-stock attribute, a dynamicpresentation attribute, can be used to identify whether specificproducts are actually available in a supplier's inventory, and theircorresponding prices and/or currencies. A search result list can beorganized by category and/or vendor based on end user preferences. Also,icons can be used to further display and highlight relevant informationregarding products such as, for example, whether products are hazardous,toxic, poisonous, or are considered to be controlled substances. Aproprietary taxonomy can also be implemented against modeling productcategories to enable more efficient searching and, ultimately,user-friendly, organized search results.

FIGS. 8A-8D illustrate exemplary search engines in accordance with thepresent invention. For example, FIG. 8A illustrates an exemplaryparametric search engine 810 and punch-out catalogs 820. FIG. 8Billustrates an exemplary quick order search engine 830. FIG. 8Cillustrates an exemplary browsing engine based on suppliers. FIG. 8Dillustrates an exemplary browsing engine based on categories of theproducts and/or services. Other search engines may be used withoutdeparting from the scope of the present invention. Therefore, aneProcurement system in accordance with the present invention couples theconfiguration tools described above for customizing access to specifiedsuppliers and/or specified types of products based on department,position, roles, and/or permissions of the user for each organizationwith various search engines in a single instance, multi-tenantarchitecture.

As shown in FIG. 2, the supplier user interface 214 in accordance withthe present invention and further described below is configurable bysupplier users and super users, and includes one or more features, forexample, such as accessing a supplier hosted products catalog, viewingand responding to purchase orders, consummating sales transactions,viewing and responding to status queries, and setting supplier userconfiguration preferences. Each individual end user and supplier usermay have a different interface from another end user and supplier user,respectively. Furthermore, the supplier end user interface of thepresent invention may allow a plurality of supplier users to sendqueries/requests via middleware/web methods server 224 to customdatabase servers 222, and to a hosted supplier products catalog 234 thatis multi-tenant managed. A remote supplier user query/request is sentvia the supplier end user interface 214 over the Internet, or othernetworked connection, and is first received by the web servers 225 afterpassing through the firewall 218. Then, the web server 225 passes thequery/request to the middleware/web methods server 224, where businessrules may be enforced. Subsequently, depending on whether thequery/request is related to a transaction or a user search, it is eitherforwarded to the transaction processing servers 223 or custom databaseservers 222, respectively. For either type of query/request, the hostedsupplier products catalog 234 is then readily accessible via processingmodules for exchanging transaction/product data, or performing asearch/supplier operation. The hosted supplier products catalog 234 canserve as a quasi-link between the end user interface and the supplierinterface because it is accessible by both interfaces. Supplier userscan access the catalog via the middleware/web methods servers 224, whichthen forward the supplier access request to the custom database servers222 and processing modules for execution, in order, for example, toupdate their own supplier data. End users may be able to search multiplesuppliers within the catalog via the end user interface 212, subject toaccess rules set by a super user. End users may search the catalog forspecific end user product requirements via the middleware/web methodsservers 224, which forward the end user search request to customdatabase servers 222 and processing modules for execution. Subsequently,the end user may then invoke requisition and purchase orders via themiddleware/web methods servers 224, which forward the end user order tothe transaction processing servers 223 for execution.

As described above, to support the product search function, theeProcurement system of the present invention includes a master catalogdatabase of all the products from all the suppliers hosted on the systemto implement a single instance, multi-tenant environment. Accordingly,the eProcurement system of the present invention includes a catalogmanagement tool 900. The catalog management tool 900 includes one ormore of supplier tool 910, categories tool 920, supplier classificationtool 930, category classification tool 940, product views tool 950,pricing tool 960, map attributes tool 970, and consortium managementtool 980.

FIG. 9A illustrates an exemplary catalog management tool 900 with anexemplary supplier tool 910 invoked. The supplier tool 910 includes asearch engine that searches for existing suppliers hosted in theeProcurement system of the present invention. Furthermore, the suppliertool 910 adds new suppliers not yet hosted in the system. FIG. 9Billustrates an exemplary categories tool 920 that configures all theproducts offered from the hosted suppliers into defined categories.Classifications for suppliers and product categories within the systemof the present invention are defined and managed by the supplierclassification tool 930 (FIG. 9C) and category classification tool 940(FIG. 9D). In particular, new classes of suppliers and productcategories may be created, defined, and configured as needed through thesupplier classification tool 930 and category classification tool 940.In addition, existing classifications of suppliers and productcategories may be modified. The product views tool 950 manages the viewsof products based on the defined supplier and product categories (FIG.9E).

FIG. 9F illustrates an exemplary pricing tool in accordance with thepresent invention. As shown, pricing tool 960 manages various pricingsets of each hosted supplier for the hosted products (or, the tool 960may also be applied to non-catalog items, forms, or other non-hostedsuppliers or products/items). The pricing set types may includeorganizational prices, contract prices, list prices, and consortiumprices. Other pricing sets may be used without departing from the scopeof the invention. The pricing tool 960 tracks versions of each type ofpricing sets, status of the pricing sets (e.g., implicitly approved, notreviewed, rejected, approved, etc.), as well as the audit history ofeach pricing set. Accordingly, the appropriate pricing set may betracked, managed, and invoked for each organization for each type ofproduct.

Other types of catalog management tool 900 include the map attributetool 970 and consortium tool 980. The map attribute tool 970 managesvarious parameters of the procurement activity, such as product codes,parameter format, and unit of measure (UOM). For example, commodity codeconfiguration parameters may be set through the map attribute tool 970to determine if and how the category taxonomy is to be mapped to, forexample, an organization's set of category/commodity values. Thecommodity codes may be modified as categories, sub-categories, and ondown to the product level. The list of values may be set manually orimported/exported from/to an already existing file. As another example,universal product codes (e.g., UN/SPSC) and UOM may also be configuredto be mapped to an internal organization codes for automatic conversionwhen searching, viewing, and ordering products. Further, UOM may bemapped from standard UOM to organization specific UOM. The consortiumtool 980 defines various consortiums that an organization may be amember of and offer consortium pricing by designating a supplier as aconsortium supplier. Hence, all organizations that are members of theconsortium will be offered the consortium pricing set when ordering fromthe designated supplier.

As shown in FIG. 2, the server technology of the present inventionincludes a middleware/web methods server 224 that hosts a variety offeatures related to administrative services management, contentmanagement, and application management described above. Themiddleware/web methods server 224 may, for example, manage businessrules (i.e., the relationships) between end users and suppliers based,in part, on contractual terms or other arrangements, as processedaccording to the price and file management feature. For example,supplier user-side business rules may, for example, designatepreferences regarding delivery terms (e.g., restrictions against odd lotsales, FOB preference, carrier preference, etc.), and price andinsurance terms (e.g., CIF preference, applicable sales tax, etc.).Similarly, end user-side business rules may, for example, designatepreferences regarding preferred suppliers, delivery terms (e.g., FOBpreference, default quantity, carrier preference, etc.), and price andinsurance terms (e.g., CIF preference, applicable sales tax, etc.). Atleast one advantage of implementing end user-side and supplier user-sidebusiness rules is the capability to generate customized purchase ordersin accordance with contractual or default business rules. Such purchaseorders are created by the invoke requisition/purchase orders feature,which is invoked via processing modules that are executed on the customdatabase servers 222. Middleware/web methods server 224 may applydefault ordering, sales, delivery, and other terms in the instance wherean end user and supplier user do not have existing contractual terms orother arrangements.

The middleware/web methods server 224, as well as the transactionprocessing server 223, implements the price and file management featureto access existing contracts between end users and suppliers. Thefeature is usually implemented as a component of the middleware/webmethods server 224, but may also be invoked via transaction processingmodules that are executed on the transaction processing servers.Contract management algorithms may also be implemented as a sub-featureof the price and file management feature. For example, the algorithmsare usually responsible for accessing, retrieving, and processing datafrom each respective end user and supplier that might have negotiated acontract. FIG. 10 illustrates an exemplary contracts management tool1000 that may be used to manage the contracts between an organizationand a supplier. The contract data is accessible by the transactionprocessing servers 223 and transaction database 238. Suppliers are ableto submit product prices and other product related data via the priceand file management feature. Furthermore, multiple pricing/currencyschemes can be created by suppliers for end user organizations and maybe based on contractual terms negotiated between end user organizationsand suppliers. Individual end users within the same organization, forexample, may be assigned different price/currency schemes that may bebased on different contractual terms with an individual supplier. Adesignated end user (e.g., a “contract manager”), akin to a super user,can be assigned the responsibility for managing and choosing the pricingschemes displayed to each individual end user within the organization.The designated end user may also be tasked with ranking the spendingthresholds for triggering a new price tier. Individual end users arecapable of accessing pricing schemes for supplier products where the endusers have been granted access by the designated end user or super user.By default, the lowest supplier pricing scheme available is firstdisplayed to the end user, although other pricing schemes may also beavailable and accessible.

The following algorithm, for example, may be implemented to determinewhich pricing scheme should be displayed to an individual end user.First, all pricing schemes for a specific product may be denoted asaccessible. A filter-type method may then be used to exclude pricingschemes denoted as inaccessible to the end user organization and, thus,allowing only accessible pricing schemes. Another filter-type method maybe used to determine which accessible pricing schemes, if any, arerelated to contracts negotiated between the end user organization andaccessible suppliers. If no pricing schemes are related to anycontracts, then a default/general pricing scheme is displayed to the enduser. Finally, if at least one pricing scheme is related to any relatedcontracts, then a filter-type method excludes those pricing schemesrelated to contracts deemed inaccessible to this end user, and permitsthe accessible pricing schemes to be displayed. The displayed accessiblepricing schemes would, however, be subject to the end user spendingthresholds, which may be set by a super user. When an end user invokesthe generation of a purchase/requisition order, the appropriate pricingscheme is referenced and can be based upon available contractual termswith the appropriate supplier.

An end user organization can manage pricing schemes such that distinctcontracts are assigned to specific end users or super users. The featureto manage pricing schemes is invoked via transaction processing modulesexecuted on the transaction processing servers 223. The specific endusers or super users have the ability to approve or reject contracts,and set extended dates. Moreover, supplier users have the ability tocreate multiple pricing/currency schemes that may be based oncontractual terms with end user organizations. Whether an individual enduser/organization is a constituent of a trade group, department, orother organization, may influence the pricing/currency schemedetermination. Supplier users can also have the ability to load singleor multiple pricing/currency schemes for end users within the same datasink (e.g., hosted supplier products catalog), which may later beprocessed by the price and file management feature and assigned to eachrespective end user. Moreover, end users can designate specific productsfrom supplier pricing/currency schemes as favorites. End user favoritescan be dynamically updated with the lowest available supplier pricingscheme.

The transaction processing servers 223 of the present invention mayexecute transaction processing modules that query, update, and/or createdata model instances within the transaction database 238. Moreover, endusers can also approve, request to modify, or reject supplier productswithin hosted catalogs, and can also assign and route specific supplierproducts to other appropriate end users for review, dependent upon enduser specific attributes like title within the organization. Forexample, certain end users may be able to access hazardous and/orexpensive supplier products, while other end users may not be able to doso based on their precedence/role within the end user organization.Similarly, certain end users may also have the ability to makehigh-volume orders, while others may not. The hosted supplier productscatalog 234 may be routinely updated by each supplier user at his/herdiscretion, or on a monthly, quarterly, or annual basis, and may containdata from suppliers such as, for example, custom product lists and enduser organization-specific prices/currencies.

FIG. 11A illustrates an exemplary cart and requisition tool 1100 inaccordance with the present invention. As shown in FIG. 11A, the cartand requisition tool 1100 includes an active cart 1140 for tracking theitems designated for purchase from the search results described above.In an exemplary embodiment illustrated in FIG. 11A, the active cart 1140includes requisition workflow tool 1110 that displays a live view of therequisition process for the items in the cart. For example, therequisition workflow tool 1110 displays the status of the requisitionfrom the point at which a product is added 1110 a, the cart is edited1110 b, the requisition is reviewed 1110 c, and the order is placed 1110f. The requisition workflow tool 1110 further displays a purchaserequisition approval step 1110 d as well as a purchase order previewstep 1110 e. Each of the status boxes 1110 a-1110 f of the requisitionworkflow tool 1110 may be invoked to activate the tool that manages thecorresponding status. For example, invoking the “Add Products” box 1110a (e.g., clicking on the box) activates the search engine to search foradditional products to be added to the cart 1140. Invoking the “EditCart” box 1110 b activates the active cart 1140 for editing the productsin the cart. Invoking the “Review” box 1110 c activates a summary of theproducts included in the requisition, including, for example, accountingcodes, billing and shipping addresses, and other customizable dataelements that may be configured by the user's organization. Invoking the“PR Approvals” box 1110 d displays the set of workflow/approval steps aninvoked requisition will be processed through prior to order creation.Invoking the “PO Preview” box 1110 e activates a list of purchase ordersthat are generated if the invoked requisition is approved. Invoking the“Place Order” box 1110 f submits the invoked requisition to the steps ofthe workflow/approval process.

Cart information 1120 such as cart name 1120 a, description 1120 b,priority 1120 c, and assigned approver 1120 d are also displayed and maybe edited. The cart information 1120 further includes supplier and lineitem details organized alphabetically, for example, according to eachsupplier's name, and lists each chosen product description, catalognumber, size and/or packaging data, unit price, quantity ordered, price,and currency. For each supplier there is also a corresponding suppliersubtotal that is calculated according to the total of products chosen bythe user.

FIG. 11B illustrates further details of the exemplary cart andrequisition tool 1100 in accordance with the present invention. Asshown, the cart and requisition tool 1100 includes a requisition reviewtool 1150, purchase request approval tool 1160, and purchase orderpreview tool 1170. As described above, the various status boxes (e.g.,1110 c-1110 e) in the requisition workflow tool 1110 activate thecorresponding tool 1150-1170. As shown in FIG. 11B, the requisitionreview tool 1150 displays information about the requisition being built.For example, as shown, the requisition review tool 1150 includes asummary page 1150 a that displays all the information regarding therequisition being reviewed, such as the general information, shippinginformation, billing information, accounting codes, internal/externalnotes and attachments, as well as supplier/line item details of theproducts in the cart 1140. All of the information shown in therequisition summary page 1150 a may be edited by invoking thecorresponding tool, such as the shipping/handling tool 1150 b, billingtool 1150 c, accounting code tool 1150 d, notes and attachment tool 1150e, supplier information tool 1150 f, and taxes/S&H pricing tool 1150 g.

For instance, the shipping/handling tool 1150 b may be used to set theshipping address of the products in the purchase order as well asdesignate delivery options, such as “expedite,” “shipping method,” and“requested delivery date.” The billing tool 1150 c may be used to setthe billing address and billing options, such as accounting dates. Theaccounting tool 1150 d may be used to designate the accountinginformation of the requisition, such as any fund/grant contacts,organization information, account numbers, product codes, activitysummaries, and location. The notes and attachments tool 1150 e may beused to designate any internal codes associated with the products in thepurchase order, such as custody codes and equipment codes used in theorganization. The supplier information tool 1150 f may be used to assignor modify supplier information for the products in the order, such ascontract information with the supplier, purchase order number, quotenumber, and purchase order clauses. The taxes/S&H tool 1150 g may beused to define the tax/S&H information related to purchases from aparticular supplier, such as tax percentage and/or S&H cost from totalpurchase price (e.g., 0% tax, free shipping if over $200 purchase,etc.).

FIG. 11C illustrates an exemplary purchase request approval tool 1160that corresponds to the purchase requisition approval step 1110 d inaccordance with the present invention. The exemplary purchase requestapproval tool 1160 graphically portrays the status of the requisitionbeing reviewed (e.g., submission of the purchase requisition 1160 a,financial approval 1160 b, supplier approval/processing 1160 c, LPO 1160d, purchase order creation 1160 e, and completion 1160 f). As with therequisition workflow tool 1110 (FIG. 11B), each workflow/approval stepstatus box may be invoked to activate a tool, corresponding to eachworkflow/approval step, to view the reason(s) underlying the workflowengine's invocation of that step. Other intervening or superseding stepsmay also be portrayed without departing from the scope of the presentinvention.

FIG. 11D illustrates an exemplary purchase order preview tool 1170 thatcorresponds to the purchase order preview step 1110 e in accordance withthe present invention. The purchase order preview tool 1170 permits theuser to preview the purchase orders that will be generated from thecurrent active cart 1140. The active cart 1140 corresponding to thatuser is queried and the preview purchase orders are displayed, as shown,in alphabetical order according to supplier name. Other methods ofordering or retrieving the purchase orders corresponding to the user mayalso be used without departing from the scope of the present invention.

With reference to FIG. 2, the feature to invoke purchase/requisitionorders may be hosted on the middleware/web methods servers 224 andmanaged by the eProcurement architecture of the present invention suchthat it is executed consistently with end user and supplier userbusiness rules as described above. From a high-level point-of-view, thisfeature is implemented based on whether the order information sought tobe processed by an end user is internal to the organization or supplierrelated. If the information is internal, it is processed accordingly viathe end user 212, the middleware/web methods servers 224, through to thecustom database servers 222, and then to the hosted supplier productscatalog 234; otherwise, the information is processed similarly exceptthat the appropriate supplier related databases (e.g., the masterproduct database 236, and the transaction database 238) may also beinvoked. During the processing of internal information, the orderinformation sought to be processed may also be directly posted (e.g.,locally to an end user).

An auto purchase order feature is available via the middleware/webmethods servers 224 and is invoked via transaction processing modulesexecuted on the transaction processing server 223, and can populateentries of a purchase order in accordance with applicable end user andsupplier contractual terms. The auto purchase order feature allows forthe generation of distribution, and payment, rule-based purchase ordersbased on the customizations effectuated by a super user of theorganization in the manner described above. For example, the feature canautomatically insert legal terms (e.g., the right to cure productdefects, what constitutes rejection and/or revocation of an order, whatmay constitute a material defect, the seller's return policy, thebuyer's acceptance policy, etc.), as well as other non-legal terms andconditions (e.g., preferred delivery dates, shipping and handlinginstructions, appropriate contact/authorized personnel, payment andreceipt of payment instructions, etc.), based on a contract that may bein place between an end user organization and a supplier. If no contractis in place, then the auto purchase order feature may prompt the user orautomatically insert default terms and conditions, whether legal ornon-legal. The feature may create receipts for each end user initiatedtransaction/purchase order and add multiple transactions/purchase ordersto a single receipt. For capable suppliers, automated responses can beaccepted for display to the end user. Such automated responses mayinclude, for example, order acknowledgement and advanced shippingnotice. Also, a document search sub-feature allows searching anyexisting transactions/purchase orders. The auto purchase order featurealso supports supplier pricing schemes modeled using the U.S. Dollar aswell as all other currency types (e.g., Euro, Yen, Pound, Peso, etc.).

FIG. 12 illustrates an exemplary workflow setup tool in accordance withthe present invention. As shown, the workflow setup tool 1200 includesrequisition workflow tool 1210, purchase order setup tool 1220, andfulfillment setup tool 1230. These tools are used to setup variousaspects of the workflow process as described above. For example, asshown in FIG. 12, the purchase order setup tool 1220 may be used todesignate the names of approvers to review and approve purchase ordersfor a particular organization. As shown, the approver list may becustomized for different departments (e.g., Math), types of products(e.g., non-catalog item), and even for specific users. Similarly, therequisition setup tool 1210 and fulfillment setup tool 1230 may be usedto designate approvers for requests and fulfillment processes,respectively. Other workflow parameters may be further defined withoutdeparting from the scope of the present invention.

FIG. 13 illustrates an exemplary purchase order approval tool inaccordance with the present invention. As shown, purchase order searchengine 1310 searches through all of the purchase orders generated by theeProcurement system of the present invention for each of the hostedorganizations. The results of the search may be filtered based ondisplay criteria such as “Approver” (e.g., user responsible forapproving the document), “Approval Queues,” “All Pending Requisitions,”“Urgent Approvals,” “Unassigned Approvals,” “Future Approvals,” and“Manual Filter” options. The result list of the purchase orders aredisplayed in the display portion 1320 with such information as P.O.number, status of the P.O., priority level of the P.O., the date/time ofthe submission for approval, the name of the requester, the designatedsupplier, the amount, and selectable options. Using the purchase orderapproval tool, the approvers as well as the requisitioners may monitorthe status of the requests and ascertain where the request is in theworkflow process. Using the tools described above, the user may drilldown to the lowest level of the request to determine what needs to bedone to move the request along if it becomes bottlenecked in theprocess, for example.

At the conclusion of the ordering process, an approval/rejection oforders feature may be implemented also through the middleware/webmethods server 224, as well as the transaction processing server 223.The approve/reject order feature is invoked via a transaction processingmodule that is executed on the transaction processing servers 223. Thisfeature can be managed by the middleware/web methods server 224 suchthat it is executed consistently with end user and supplier userbusiness rules. For example, one advantage of this feature is itsability to provide notice of an approved or rejected order to an enduser or super user.

FIG. 14 illustrates an exemplary history tool in accordance with thepresent invention. The eProcurement system in accordance with thepresent invention keeps a history of all requests, purchase orders,receipts, invoices, and actions (e.g., edits to parameters) made in thesystem that may be searched and reviewed. History tool 1400, forexample, includes a tool to search for purchase order histories,purchase request histories, receipt histories, and invoice histories.The searches may be made by purchase order number, by requisition, bysupplier/SKU numbers, by receipts, by invoices, and by contracts. Theseparameters may be filtered by dates, users, as well as other specificsof the history being sought.

Finally, a supplier configuration feature may be implemented. Thisfeature allows for the capability to have a supplier master that hostsmultiple fulfillment centers. Also, this feature allows for an orderprocessing feature with multiple payment/currency methods for eachfulfillment center, the execution of shipping and handling rules, andorder distribution features. The order distribution features can includesuch features as facsimile or email confirmation, as well as otherdelivery methods, organized hierarchically to ensure purchase orderdelivery.

FIG. 15 is a block diagram of the electronic procurement system 20communicating over a network 16 with suppliers 214-A (to 214-N) andpurchasing organizations 212-A (to 212-N). The electronic procurementsystem 20 generally includes a supplier server application 1542 andpurchaser server application 1550, which may interface with the accessengine 21, contract engine 1554, search/catalog engine 22, requisitionengine 23 a, order/payment engine 23 b, tracking engine 23 c, andbusiness rules engine 24.

As described, business rules describe and control the relationshipsbetween end users and suppliers based, in part, on contractual terms orother arrangements, as processed according to the price and filemanagement feature. For example, supplier user-side business rules may,for example, designate preferences regarding delivery terms (e.g.,restrictions against odd lot sales, FOB preference, carrier preference,etc.), and price and insurance teems (e.g., CIF preference, applicablesales tax, etc.). Similarly, end user-side business rules may, forexample, designate preferences regarding preferred suppliers, deliveryterms (e.g., FOB preference, default quantity, carrier preference,etc.), and price and insurance terms (e.g., CIF preference, applicablesales tax, etc.). At least one advantage of implementing end user-sideand supplier user-side business rules is the capability to be able togenerate customized purchase orders, in accordance with contractual ordefault business rules.

Non-limiting examples of business rules may include:

-   -   If the extended price of any line item exceeds the limit set in        a user's profile, route to the user's financial approver.    -   If the total value of the requisition exceeds the limit set in a        user's profile, route to the user's financial approver.    -   If a requisition sent to a user for financial approval exceeds        the user's approval authority set in the user's profile, route        the requisition to the user's financial approver.    -   If the requisition contains suppliers classified by a user's        organization as “IT Vendors,” send the requisition to the CIO.    -   Requisitions for the Math Department over $10,000 are routed to        the Vice Chancellor of Liberal Arts.    -   If any item on the PO is radioactive, route the PO to the        environmental health and safety (EH&S) Department for review and        approval.    -   If any item on the PO is classified as hazardous, notify the        EH&S Department. No approval is required.    -   If the account code for a line item on the requisition has a        budget, and the requisition will exceed the budget, route the        requisition to the Budget Manager.    -   If the user adds a non-catalog item to their requisition, route        it to the Purchasing Department to validate the information        entered.    -   If a requisition is marked for expediting, skip all rules and        route directly to the Purchasing Department.    -   All the above examples of business rules are exemplary and not        intended as limiting.

The supplier server application 1542 and purchaser server application1550 may also interface with the transaction engine 23, which mayinclude the requisition module 23 a, order/payment engine 23 b, and thetracking engine 23 c. Moreover, the supplier server application 1542 andpurchaser server application 1550 may send and receive data from thedata repository 30, which includes the user database 32, the productindex database 34, the product database 36, and the transaction database38. The engines may communicate via function/method calls, filelibraries, and database queries. The contract engine 1554 executes thenecessary functions for implementing the contract management feature,which manages and links new or existing procurement contracts, formedbetween buyer organizations and supplier organization, with a group. Forexample, a new or existing contract is initially stored in the contractsdatabase 3200 (as described in FIG. 32) and may routinely be updated inaccordance with amendments (e.g., extensions, additions of agreed uponterms, assignments, or the like) or other contractual events (e.g., theexpenditure of quantity/time/spending limits (i.e., tiers), pricefluctuations—e.g., rebates or price reductions, item changes oradditions, etc.); at such time intervals as determined by the contractengine 1554, the group is updated accordingly. The group includes, forexample, buyer users, supplier users, the business rules engine 24,items, forms, purchase requisitions/orders, sales orders/invoices, andbuyer invoices. Furthermore, the contract engine 1554 also supportscontract searching (as described in FIG. 10) based on specificuser-specified criteria like, for example, contract number, contractkeyword, or supplier/catalog name.

The supplier server application 1542 communicates with a supplier 214-A(to (214-N) over network 16 and the purchaser server application 1550communicates with a buyer 212-A (also referred to herein as a purchasingorganization) over network 16. A supplier user would use a clientapplication 1516-A (to 1516-N) to communicate with, generally, theelectronic procurement provider 20 and, specifically, the supplierserver application 1542. The client application 1516-A (to 1516-N) maybe a web-browser 1518-A (to 1518-N) for the supplier user to use, or maybe a standalone application. The web-browser 1518-A or standaloneapplication may display features to manage catalog(s) 1512-A (to 1512-N)and manage sales 1514-A (to 1514-N), which may be communicated via thesupplier server application 1542 and displayed to the supplier user. Abuyer user would use a client application 1532-A (to 1532-N) tocommunicate with, generally, the electronic procurement provider 20 and,specifically, the purchaser server application 1550. The clientapplication 1532-A (to 1532-N) may contain a web-browser 1538-A (to1538-N) for the buyer user to use, or may be a standalone application.The web-browser 1538-A or standalone application may display features tomanage purchasing 1533-A (to 1533-N), manage payment 1534-A (to 1534-N),manage users 1535-A (to 1535-N), manage privileges 1536-A (to 1536-N),and/or manage business rules 1537-A (to 1537-N), which may becommunicated via the purchaser server application 1550 and displayed toa buyer user. For example, a user that sends a request to the system 20that is outside the scope of that user's privileges would receive anappropriate denial response from the system 20 and, more specifically,for example, from the manage privileges 1536-A feature.

FIG. 16 is a block diagram of the buyer 212 communicating with thepurchaser server application 1550, located at the electronic procurementprovider 20, over a network 16. The purchaser server engine 1650 mayinterface with or include the following modules, or a subset thereof:

-   -   a catalog engine 1655 for managing each supplier catalog by        implementing features for uploading catalog data, linking to the        proper punch-out catalog(s) (1656) via the punch-out module 22 a        and back to the buyer, managing supplier showcase promotions and        overlays (1657), converting supplier catalog data into a common        data format (1658), and interfacing with the search engine 22        for searching the master product database or other accessible        database of the electronic procurement system 20;    -   an organization database 1660 for storing organization specific        information like, for example, business rules (1662),        user-related data (1663), or permissions (1664);    -   a currency engine 1670 for implementing multi-currency features        like, for example, normalizing a plurality of currency data        (1671) into a default or preferred currency, interfacing with        the search engine 22 to return item search results to a buyer        user who sent a request to organize/filter the search results        (1672) according to a specific currency, or determining the        default or preferred currency with which a supplier requests or        requires payment; or    -   a workflow management engine 1680 for managing the flow of        purchase requisitions to the appropriate approver (via the        requisition fulfillment engine 1686) (which may be prioritized        via the prioritize receipt feature 1687 based on user hierarchy,        privileges, or business rules), sending the approved requisition        back to the appropriate buyer user (via the requisition        fulfillment engine 1686), interfacing with the search engine 22        to locate an appropriate requisition and/or purchase order (via        the search PO/Invoice feature 1692), forwarding a purchase order        to the appropriate supplier (via the requisition fulfillment        engine 1686), forwarding a sales order and/or invoice from the        supplier to the appropriate buyer user (via the order payment        engine 1690 and using the PO/Invoice match feature 1691 for        linking a purchase order on the buyer user side with an incoming        invoice from the supplier), or sending event updates to the        contract engine 1554 (via the contract management engine 1688).    -   Moreover, the workflow management engine 1680 may also interface        with a purchasing engine 1681 that receives orders (via an order        entry feature 1682), manage the items a buyer user places in a        cart or moves/assigns to a new cart (via a cart management        feature 1683), present alternative items to a buyer in lieu of        items chosen for requisitioning that are not available according        to privileges, inventory or a contractual agreement (via an        alternative item present feature 1684), or approve an order if        approved by the appropriate approver user (via an order approval        feature 1685). In addition, the workflow management engine 1680        may also interface with a form management engine 1693 for        receiving requisitions and orders via user-created custom forms        stored in a forms database 2300. Once received, the requisitions        and orders are then routed to approvers and suppliers,        respectively, according to workflow business rules. And, the        workflow management engine 1680 also interfaces with the catalog        management feature 1695 for retrieving item data related to the        items present in the requisitions, orders, or invoices being        processed by the workflow management engine 1680.

FIG. 17 is a block diagram of the supplier 214 communicating with thesupplier server application 1542, located at the electronic procurementprovider 20, over a network 16. The supplier server engine 1750 mayinterface with or include the following modules, or a subset thereof:

-   -   a catalog engine 1755 for managing each supplier catalog by        implementing features for uploading catalog data, linking to the        proper punch-out catalog(s) (1756) via the punch-out module 22 a        and back to the buyer, managing supplier showcase promotions and        overlays (1757), converting supplier catalog data into a common        data format (1758), and interfacing (1759) with the catalog        management feature 1695 for updating the master product database        or other accessible supplier-related database of the electronic        procurement system 20;    -   an item database 1790 for storing item specific information        like, for example, item description (1791), price and quantity        available (1792), restrictions (1793), or priorities (1794);    -   a supplier database 1775 for storing supplier specific        information like, for example, detailed supplier data (1776), or        supplier catalog data (1777); or    -   a sales management engine 1760 for managing the flow of sales        orders and sales invoices from the appropriate buyer to the        appropriate supplier (via the sale fulfillment engine 1770)        (which may be prioritized (via the prioritize customer feature        1771) based on buyer/user hierarchy, privileges, or business        rules), shipping (1772) and tracking (1773) the ordered item(s)        to the appropriate buyer, interfacing with the search engine 22        to locate an appropriate purchase order and/or invoice (via the        search PO/Invoice feature 1782), forwarding an invoice to the        appropriate buyer (via the sale fulfillment engine 1770),        receiving payment on an invoice from a buyer to the appropriate        supplier (via the receive payment engine 1780 and using the        PO/Invoice match feature 1781 for linking a sales order on the        supplier user side with an outgoing invoice from the supplier),        or sending event updates to the contract engine 1554 (via the        contract management engine 1784).    -   Moreover, the sales management engine 1760 may also interface        with a sales engine 1761 that receives sales orders (via an sale        entry feature 1762), manage the items (e.g., goods and/or        services) a buyer user requested via the sales order (via a        goods management feature 1763), present alternative items to a        buyer in lieu of items chosen for ordering that are not        available according to inventory or business rules like a        contractual agreement (via an alternative item present feature        1764), or approve a sales order if the item(s) is available and        complies with business rules (via a sale approval feature 1765).        In addition, the workflow management engine 1680 may also        interface with a form management engine 1783 for receiving sales        orders via user-created custom forms stored in a forms database        2300. Once received, the sales orders are then routed to the        appropriate supplier user(s), respectively, according to        workflow business rules. Then, the process of fulfilling the        order is initiated and managed by the sales fulfillment engine        1770.

FIG. 18 is a block diagram of a supplier client 214. The clientapplication 1516 may be a web-browser 1518 for the supplier user to use,or may be a standalone application. The web-browser 1518 or standaloneapplication may display features for:

-   -   managing catalog(s) 1512;    -   managing sales 1514;    -   interfacing with the catalog database 1820 to, for example,        input or view item restrictions 1821, or to make catalog updates        1822;    -   managing forms 1825 by, for example, customizing required forms        1826;    -   managing sales 1830 by, for example, entering sales data 1833,        approving sales 1834, fulfilling sales orders 1835, and        addressing disputes that may arise 1836; or    -   processing invoices and payments 1840 by, for example, sending        invoices 1841, matching purchase orders to invoices 1842, or        processing funds 1843.

FIG. 19 is a block diagram of a purchasing organization client 212. Theclient application 1532 may be a web-browser 1538 for the buyer user touse, or may be a standalone application. The web-browser 1538 orstandalone application may display features to manage purchasing 1533,manage payment 1534, manage users 1535, manage privileges 1536, ormanage business rules 1537. In addition, the web-browser 1538 orstandalone application may also display features for:

-   -   interfacing with the user database 1920 to, for example, access        or define user privileges 1921;    -   managing a buyer organization's business rules 1925 to, for        example, define preferred suppliers 1926, items 1927, or        catalogs 1928;    -   managing workflows 1930 like, for example:        -   the flow of purchase requisitions within the buyer            organization,        -   access to catalogs 1932 as may be necessary (via a purchase            engine 1931) for forwarding a purchase requisition or order            appropriately for approval,        -   order entry 1933, order approval 1934, order fulfillment            1935 (all via a purchase engine 1931), or        -   forwarding a sales order and/or invoice from the supplier to            the appropriate buyer user (via the payment engine 1940 and            using the PO/Invoice match feature 1942 for linking a            purchase order on the buyer user side with an incoming            invoice from the supplier), processing payment on the            order's invoice 1941 (via the payment engine 1940), or            forwarding of a user-customized form in accordance with            business rules.

FIG. 20 is a block diagram of a server system 2000. The server system2000 generally includes one or more processing units (CPU's) 2002, oneor more network or other communications interfaces 2004, memory 2010,and one or more communication buses 2008 for interconnecting thesecomponents. The communication buses 2008 may include circuitry(sometimes called a chipset) that interconnects and controlscommunications between system components. The server system 2000 mayoptionally include a user interface, for instance a display 2006 and aninput device 2005. Memory 2010 may include high speed random accessmemory and may also include non-volatile memory, such as one or moremagnetic disk storage devices. Memory 2010 may include mass storage thatis remotely located from the central processing unit(s) 2002. Memory2010 includes high-speed random access memory, such as DRAM, SRAM, DDRRAM or other random access solid state memory devices; and may includenon-volatile memory, such as one or more magnetic disk storage devices,optical disk storage devices, flash memory devices, or othernon-volatile solid state storage devices.

In some embodiments, memory 2010 stores the following programs, modulesand data structures, or a subset thereof:

-   -   an operating system 2011 that includes procedures for handling        various basic system services and for performing hardware        dependent tasks;    -   a network communication module 2012 that is used for connecting        the server system 2000 to other computers via the one or more        communication network interfaces 2004 (wired or wireless) and        one or more communication networks, such as the Internet, other        wide area networks, local area networks, metropolitan area        networks, and so on;    -   a catalog module 2020 that provides information and prices about        products in hosted supplier product catalogs;    -   databases 2032;    -   a staging database 2034;    -   a currency module 2040;    -   a sales/purchase management module 2046;    -   a contract management module 2060;    -   a database and management module 2070; and    -   auxiliary services modules 2090.

The catalog module 2020 may include the following modules, or a subsetthereof:

-   -   supplier catalog access module 2022 for providing suppliers with        access to their respective hosted supplier product catalogs;    -   a user local catalog create/access module 2024 for providing        users (purchasing organizations) with local catalogs, in one        embodiment generated by the respective users, from which the        users can order products from suppliers who are not associated        with hosted supplier product catalogs. In one embodiment, a        supplier in the local catalogs is a local service provider (e.g.        catering or a limousine service) from which a user wants to        order products and services using the electronic procurement        system;    -   a schema translate module 2026 for translating catalog data        provided by suppliers or purchasing data provided by users into        a common format associated with the electronic procurement        system;    -   a schema update module 2028 for updating data in the common        format associated with the electronic procurement system in        response to changes in the respective catalog data or purchasing        data; and    -   a supplier showcase module 2030 for promoting certain suppliers        to users of a purchasing organization, which in an embodiment        may be performed according to business rules.

The databases 2032 may include all databases used by the system. Thesedatabases may in one embodiment be stored as logical partitions in amemory. These databases may in another embodiment be stored as tables ina larger database. These databases may in yet another embodiment bestored in separate memory or storage devices.

The staging database 2034 may comprise a catalog development environment(i.e., a staging area) for catalogs associated with suppliers. The datain the staging area may include complete catalogs, incomplete catalogsin development, partially uploaded catalogs, etc. A supplier can chooseto make any or all portions of their respective catalog(s) in thestaging database ‘live’ by syndicating the respective portions. A livecatalog is one from which a user or purchasing organization may orderitems. The item database 2036, which may be a subset of the stagingdatabase 2034, contains descriptions, characteristics, price, picturesand other pertinent information for items listed in the catalogs.

The currency module 2040 may include the following modules, or a subsetthereof:

-   -   a normalize rates module 2042 for normalizing currency rates        visible by a purchaser of goods and/or services, purchasing from        suppliers using different currencies to that of the purchaser,        or by a supplier of goods and services selling to purchasers        using different currencies to the supplier; and    -   a filter by currency module for allowing purchasers to filter        suppliers according to currencies they do business in, or        allowing suppliers to filter purchasers similarly.

The sales/purchase management module 2046 may include the followingmodules, or a subset thereof:

-   -   a template management module 2048, for managing templates used        by suppliers or purchasers of the system in placing orders for        goods or services;    -   a cost/markup management module 2050 for determining        characteristics (e.g., average cost) of inventory and managing        the inventory based on the characteristics and a markup rate;    -   order receipt module 2052 for determining that an order has been        received, and preparing to fulfill the order;    -   sale fulfillment module 2054 for fulfilling the order, including        invoicing and shipping goods to the purchaser; and    -   a receive payment module 2056 for receiving payment associated        with an order (both for fulfilled and unfulfilled orders).

The contract management module 2060 may include the following modules,or a subset thereof:

-   -   order receipt module for 2062 for determining that an order has        been received and matching the order to a contract;    -   sale fulfillment module 2064 for associating fulfillment of an        order with a contract and verifying that the received order        complies with the contract;    -   receive payment module 2066 for associating payments with a        contract and verifying that appropriate discounts and terms of        the contract are reflected in the payment; and    -   associate contract with forms module 2068 for associating the        contract with forms used by a supplier or purchaser, such that        terms of the contract apply to the form.

The database and management module 2070 may include the followingmodules, or a subset thereof:

-   -   Access, update and manage database module 2072 for accessing,        updating and managing databases in the system, including:        -   user (purchaser) and supplier module 2074, for managing user            database 32 as described, which is accessed by a buyer user            12 or supplier user 14 through access module 21 as            described;        -   workflow, catalog and forms module 2076, for managing            workflow database 3000, catalog database 2400, and forms            database 2300 as described;        -   master, transaction and contracts module 2078, for managing            master database 236, transaction database 238 ad contracts            database 3200 as described;        -   staging module 2080, for managing staging database 3100 as            described; and        -   invoice, purchase order, order, and requisition module 2082,            for managing invoice databases 3300 and 3400, order database            2900 and 2500, requisition database 2700 as described.

The auxiliary services module may include additional features orservices related to operation, management, security, authentication,maintenance or other aspects of the electronic procurement system.

FIG. 21 is a block diagram of a server system 2100. The server system2100 generally includes one or more processing units (CPU's) 2102, oneor more network or other communications interfaces 2104, memory 2110,and one or more communication buses 2108 for interconnecting thesecomponents. The communication buses 2108 may include circuitry(sometimes called a chipset) that interconnects and controlscommunications between system components. The system 2100 may optionallyinclude a user interface, for instance a display 2106 and an inputdevice 2105. Memory 2110 may include high speed random access memory andmay also include non-volatile memory, such as one or more magnetic,optical, or solid state disk storage devices. Memory 2110 may includemass storage that is remotely located from the central processingunit(s) 2102. Memory 2110 includes high-speed random access memory, suchas DRAM, SRAM, DDR RAM or other random access solid state memorydevices; and may include non-volatile memory, such as one or moremagnetic disk storage devices, optical disk storage devices, flashmemory devices, or other non-volatile solid state storage devices.

In some embodiments, memory 2110 stores the following programs, modulesand data structures, or a subset thereof:

-   -   an operating system 2111 that includes procedures for handling        various basic system services and for performing hardware        dependent tasks;    -   a network communication module 2112 that is used for connecting        the server 2000 to other computers via the one or more        communication network interfaces 2004 (wired or wireless) and        one or more communication networks, such as the Internet, other        wide area networks, local area networks, metropolitan area        networks, and so on;    -   a web browser 2118 or other tool for providing client access and        visibility to the electronic procurement system, where in some        embodiments some or all of the operations of the electronic        procurement system are performed at a server, and in some        embodiments some of the operations of the electronic procurement        system are performed at the client;    -   a catalog module 2120 that provides information and prices about        products in hosted supplier product catalogs;    -   databases 2132;    -   a workflow module 2142;    -   a currency module 2154;    -   a contract management module 2160;    -   a database management module 2170; and    -   auxiliary services modules 2184.

The catalog module 2120 may include the following modules, or a subsetthereof:

-   -   a user local catalog create/access module 2122, in some        embodiments similar to module 2024, for providing users        (purchasing organizations) with local catalogs, in one        embodiment generated by the respective users, from which the        users can order products from suppliers who are not associated        with hosted supplier product catalogs. In one embodiment, a        supplier in the local catalogs is a local service provider (e.g.        catering) from which a user wants to order products and services        using the electronic procurement system;    -   a supplier showcase module 2124, in some embodiments similar to        module 2030, for promoting certain suppliers to users of a        purchasing organization, which in an embodiment may be performed        according to business rules;    -   a Punch Out module 2126 for providing access to a catalog or        website separate from the hosted supplier product catalogs, and        allowing a purchaser to purchase an item from that catalog or        website, and process the purchase through the electronic        purchasing system;    -   a present alternatives module 2128, for presenting alternative        items to a prospective purchaser upon determining that an item        requested by the purchaser cannot be fulfilled or that a better        item might be available; and    -   a purchaser priority module 2130 for prioritizing purchasers or        purchaser orders associated with a user or purchasing        organization.

The databases 2132 may include all databases used by the system, both onthe server side and client side. These databases may in one embodimentbe stored as logical partitions in a memory. These databases may inanother embodiment be stored as tables in a larger database. Thesedatabases may in yet another embodiment be stored in separate memory orstorage devices. The databases may include the following databases ormodules, or a subset thereof:

-   -   business rules database 2134 for storing business rules        associated with a user, purchasing organization or supplier,        wherein in some embodiments the business rules may be set by a        super-user or administrator associated with an organization;    -   user privilege database 2136 for storing privileges associated        with users, such as purchasing privileges, approval privileges,        etc.;    -   organization priority database 2138 for storing priority        information associated with users or purchasing organizations in        the electronic procurement system; and    -   user created forms/search database 2140 for storing forms,        search queries, etc associated with a user or purchasing        organization, or associated with a supplier.

The workflow module 2142 may include the following modules, or a subsetthereof:

-   -   cart management module 2144 for allowing a user or organization        to manage a shopping cart associated with the purchase of items;    -   assign/move/schedule cart module 2146 for allowing a user or        organization to assign a cart to another user, to move items        from one cart to another (including a new) cart, and to schedule        a cart for purchasing;    -   purchasing/checkout module 2148 for allowing a user to checkout        one or more carts and purchase the items in the one or more        carts;    -   order fulfillment module 2150 for verifying that an order has        been received and processed for fulfillment, wherein in some        embodiments this may be similar to sale fulfillment module 2054        for fulfilling the order; and    -   payment module/currencies 2152 for processing payment for an        order, including converting currencies if necessary.

The currency module 2154 may include the following modules, or a subsetthereof:

-   -   a normalize rates module 2156 (in some embodiments similar to        module 2042) for normalizing currency rates visible by a        purchaser of goods and/or services, purchasing from suppliers        using different currencies to that of the purchaser, or by a        supplier of goods and services selling to purchasers using        different currencies to the supplier; and    -   a filter by currency module 2158 (in some embodiments similar to        module 2044) for allowing a purchasers to filter suppliers        according to currencies they do business in, or allowing        suppliers to filter purchasers similarly.

The contract management module 2160 may include the following modules,or a subset thereof:

-   -   an order receipt module 2162 (in some embodiments similar to        module 2062) for determining that an order has been received and        matching the order to a contract;    -   a sale fulfillment module 2164 (in some embodiments similar to        module 2064) for associating fulfillment of an order with a        contract and verifying that the received order complies with the        contract;    -   a receive payment module 2166 (in some embodiments similar to        module 2066) for associating payments with a contract and        verifying that appropriate discounts and terms of the contract        are reflected in the payment; and    -   an associate contract with forms module 2168 (in some        embodiments similar to module 2068) for associating the contract        with forms used by a supplier or purchaser, such that terms of        the contract apply to the form.

The database management module 2170 may include the following modules,or a subset thereof:

-   -   Access, update and manage database module 2172 (in some        embodiments similar to module 2072) for accessing, updating and        managing databases in the system, including:        -   user (purchaser) and supplier module 2174 for managing user            database 32 as described, which is accessed by a buyer user            12 or supplier user 14 through access module 21 as            described;        -   workflow, catalog and forms module 2176 for managing            workflow database 3000, catalog database 2400, and forms            database 2300 as described;        -   master, transaction and contracts module 2178 for managing            master database 236, transaction database 238 ad contracts            database 3200 as described;        -   staging module 2080 for managing staging database 3100 as            described; and        -   an invoice, purchase order, order, requisition module 2182            for managing invoice databases 3300 and 3400, order database            2900 and 2500, requisition database 2700 as described.

The auxiliary services modules 2184 (in some embodiments similar tomodule 2090) may include additional features or services related tooperation, management, security, authentication, maintenance or otheraspects of the electronic procurement system.

FIG. 22 shows a top level data structure 2200 at an electronicprocurement provider server. The data structure includes data repository230, end user database 232, hosted supplier product index 234, masterproduct database 236, and transaction database 238. The end userdatabase 232 may in an embodiment include user/security database 3500.The hosted product index 234 may in an embodiment include summary searchdatabase 2460. The data structure further includes staging database3100, and scheduler database 3600.

The master database is associated with (and may in some embodimentsinclude one or more of) a forms database 2300 and a catalog database2400, which in an embodiment includes items database 2401 and pricesdatabase 2430.

The transaction database is associated with (and may in some embodimentsinclude one or more of) buyer invoice database 3300, sales invoicedatabase 3400, requisition database 2700, receipt database 2800, salesorder database 2900, workflow database 3000, contracts database 3200,and purchase order database 2500. The purchase order database 2500 mayin an embodiment include the fax database 2600, revisions database 2602,and distribution database 2604.

FIG. 23 shows a database diagram 2300 including the master database 236,with master database index 237 indexing into the master database. Masterdatabase index 237 includes summary search database 2460.

In an embodiment, forms database 2300 includes one or more of:

-   -   Form Config Section Title Help 2301, in some embodiments help        information for configuring a form section title;    -   Form Config Group Title Help 2302, in some embodiments help        information for configuring a form group title;    -   Form Config Element Title Help 2303, in some embodiments help        information for configuring a form element;    -   Form List 2304, in some embodiments a list of forms;    -   Form Config Section 2305, in some embodiments configuration of a        form section;    -   Form Config Group 2306, in some embodiments configuration of a        form group;    -   Form List Value 2307;    -   Form Config Element 2308, in some embodiments configuration of a        form element;    -   Form Config Version 2309, in some embodiments configuration of a        form version;    -   Form User Defined Fields 2310, in some embodiments user defined        fields in a form;    -   Form User Defined Field Config Parameters 2311, in some        embodiments parameters for configuring user defined fields in a        form;    -   Form List Value Title Help 2312;    -   Form 2313;    -   Form Audit Trail 2314, in some embodiments a list of changes to        a form for auditing purposes;    -   Forms User Defined Field Data 2315;    -   Forms Up Dist Method 2316, in some embodiments forms update        distribution method details; and    -   Forms Up Dist Method Data 2317, in some embodiments forms update        distribution method data.

FIG. 24 shows a database diagram 2400 including the master database 236,with master database index 237 indexing into the master database. Masterdatabase index 237 includes summary search database 2460.

As described, the search architecture is based upon an indexed,tokenized-type implementation. This search architecture may include asearch engine and a tokenization feature, both of which are invoked viaprocessing modules executed on the custom database servers. Productelements such as the product name, industry, price, and availability,among others, are primarily used to generate a product search index(e.g., a token). The process of generating a product search index/tokenis called “tokenization” and may be executed by a tokenization featureinvoked via a processing module. The indices/tokens generated as aresult of the tokenization feature, which relate to various products ofa multitude of suppliers, may be stored within and executed on thehosted supplier products catalog. Searching is actually executed againstwhat are termed as “verticals.” A vertical is designed similar to adrill-down menu architecture that consists of root nodes and leaf nodes,which are children of their respective roots.

The forms database 2300, and catalog database 2400 are associated withthe master database. The catalog database includes items database 2401and price database 2430.

In an embodiment, items database 2401 includes one or more of thefollowing:

-   -   Item Attribute Attr Value 2402, in some embodiments a value for        an item attribute;    -   Item Attribute Valid Values 2404, in some embodiments valid        values value for an item attribute;    -   Item Attribute Audit Trail 2406, in some embodiments a list of        changes to an item attribute for auditing purposes;    -   Item Attribute Definition 2408;    -   Item Attribute Data 2410;    -   Item 2412;    -   Chem Structure 2414, in some embodiments a description of a        chemical structure that may be ordered through the procurement        system;    -   Chem Structure Supplier 2416, in some embodiments a supplier of        a chemical structure;    -   Item Chemical 2418, in some embodiments a commercial item of a        chemical structure, e.g., a container of a certain chemical        structure.    -   Supplier 2420;    -   Item Image Description 2422, in some embodiments a description        of an image or picture associated with an item;    -   Item Image File Data 2424, in some embodiments an image data        file (e.g., a JPEG image or GIF image, as commonly used in web        applications);    -   Item Inventory Config 2426, in some embodiments data for        configuring inventory of an item; and    -   Item Inventory Config Audit Trail 2428, in some embodiments a        list of changes to data for configuring inventory of an item.

In an embodiment price database 2430 includes one or more of thefollowing:

-   -   Item 2432, in some embodiments an item for which a price is        stored in the price database;    -   Supplier 2434, in some embodiments a supplier associated with        the item;    -   Item Attribute Audit Trail 2436, in some embodiments a list of        changes to an attribute associated with an item, for which a        price is stored in the price database;    -   Price Set Org Details 2438, in some embodiments details of an        organization price;    -   Price Set 2440, in some embodiments a price for the item;    -   Price Version Approval 2442, in some embodiments approval for a        version of a price associated with the item;    -   Price Version 2444, in some embodiments a version of a price        associated with the item;    -   Price Set Version 2446;    -   Price 2448, in some embodiments a price for the item;    -   Submission Price Component 2450;    -   Price Version Loading Submission 2452;    -   Submission Audit Trail 2454, in some embodiments for auditing        submissions; and    -   Submission 2456.

In an embodiment summary search database 2460 includes one or more ofthe following:

-   -   Supplier Price Date 2402, in some embodiments a date associated        with a supplier price;    -   Supplier Content Date 2404, in some embodiments a date        associated with supplier content (e.g., description);    -   Organization 2406;    -   Supplier 2408, in some embodiments a supplier of an item;    -   Searchable Verticals By Rule 2470, in some embodiments        supporting rule-based searching;    -   Product Rule 2472, in some embodiments a rule related to a        product;    -   Product Vertical 2474, in some embodiments supporting        product-based searching;    -   Org Supplier Item Counts 2476, in some embodiments a count of        items stored at an organization supplier;    -   Product Category 2478, in some embodiments a category related to        a product;    -   Supplier Category Summary 2480, in some embodiments a summary of        a supplier category;    -   Item Incr Indexing Queue 2482, in some embodiments a queue for        incrementally indexing items;    -   Org Favorites Full Indexing Queue 2484, in some embodiments a        full-indexing queue for organizational favorites; and    -   Org Favorites Incr Indexing Queue 2486, in some embodiments an        incremental-indexing queue for organizational favorites.

FIG. 25 shows a database diagram 2500 including the transaction database228, with transaction database index 229 indexing into the transactiondatabase 228. Transaction database 228 is associated with (and in someembodiments includes one or more of) the following databases:

-   -   Purchase Order (PO) DB 2500, in some embodiments a database of        purchase orders;    -   Fax DB 2600, in some embodiments a database of faxes;    -   Distribution DB 2602, in some embodiments for storing order        distributions, where the order distribution features can include        such features as facsimile or email confirmation, as well as        other delivery methods, organized hierarchically to ensure        purchase order delivery, as described;    -   Revisions DB 2604, in some embodiments for storing revisions to        sales or purchase documents;    -   Buyer Invoice DB 3300, in some embodiments for storing buyer        invoices;    -   Seller Invoice DB 3400, in some embodiments for storing seller        invoices;    -   Requisition DB 2700, in some embodiments for storing purchase        requisitions;    -   Receipt DB 2800, in some embodiments for storing receipts;    -   Sales Order DB 2900, in some embodiments for storing sales        orders;    -   Workflow DB 3000, in some embodiments for storing workflow data        relating to sales, purchases and transactions, etc.; and    -   Contracts DB 3200, in some embodiments for storing contracts.

In an embodiment, Purchase Order (PO) DB 2500 includes one or more of:

-   -   Config Section Title Help 2502, in some embodiments help        information for configuring a section title;    -   PO Config Group Title Help 2504, in some embodiments help        information for configuring a purchase order group title;    -   PO Config Element Validation 2506, in some embodiments        validation information for configuring a purchase order element;    -   PO Audit Trail 2508, in some embodiments a purchase order audit        trail;    -   PO WF Activity History 2510, in some embodiments a purchase        order workflow activity history;    -   PO Config Group 2512, in some embodiments configuration of a        purchase order group;    -   PO Config Section 2514, in some embodiments configuration of a        purchase order section;    -   PO Config Element 2516, in some embodiments configuration of a        purchase order element;    -   PO Config Version 2518, in some embodiments configuration of a        purchase order version;    -   PO Config 2520, in some embodiments configuration of a purchase        order;    -   PO Summary 2522, in some embodiments a purchase order summary;    -   PO Dist Method Data 2524, in some embodiments data for a        purchase order distribution method;    -   PO Dist Method 2526, in some embodiments a purchase order        distribution method;    -   PO 2528, in some embodiments a purchase order;    -   PO Currency Exchange Rates 2530;    -   Supplier 2532;    -   Fulfillment Center 2534;    -   PO User Selected Approver 2536, in some embodiments a        user-selected approver for a purchase order;    -   PO Pending Actions 2538, in some embodiments pending actions        relating to a purchase order;    -   PO PO Clauses 2540, in some embodiments clauses relating to a        purchase order;    -   PO Line Search 2542, in some embodiments line search details        relating to a purchase order;    -   PO Line 2544, in some embodiments a line of a purchase order;    -   Req Line Address 2546, in some embodiments an address line        relating to a purchase requisition;    -   PO Line Product 2548, in some embodiments a product line        relating to a purchase order;    -   PO Credit Card 2550, in some embodiments a credit card        associated with a purchase order;    -   PO Line Report 2552, in some embodiments a report line relating        to a purchase order;    -   PO CF Value Set Values 2556, in some embodiments to set the        value of a custom field value in a purchase order;    -   PO CF Value Set Ctxt 2558, in some embodiments to set the        context of a custom field value in a purchase order;    -   PO CF Value Set Def 2560, in some embodiments to set the        definition of a custom field value in a purchase order; and    -   PO User Selected Approver 2562, in some embodiments a        user-selected approver of the purchase order.

FIG. 26 shows a database diagram 2600 including the transaction database228, with transaction database index 229 indexing into the transactiondatabase. The fax database 2600, distribution database 2602 andrevisions database 2604 are associated with the transactions database228.

In an embodiment, the fax database 2600, distribution database 2602 andrevisions database 2604 include one or more of:

-   -   PO Fax Config Section 2610, in some embodiments configuration of        a purchase order fax section;    -   PO Fax Config Group 2612, in some embodiments configuration of a        purchase order fax group;    -   PO Fax Config Element 2614, in some embodiments configuration of        a purchase order fax element;    -   PO Fax Config 2616, in some embodiments configuration of a        purchase order fax;    -   PO Fax Config Version 2618, in some embodiments configuration        version of a purchase order fax;    -   PO Revision Document Relationship 2620, in some embodiments a        document relationship of a purchase order revision    -   PO Revision 2622, in some embodiments a purchase order revision;    -   PO Dist Request 2624, in some embodiments a purchase order        distribution request;    -   PO Dist Entry Data 2626, in some embodiments purchase order        entry data;    -   PO Revision Document 2628, in some embodiments a purchase order        document revision;    -   PO Dist Entry 2630, in some embodiments entry of a purchase        order distribution;    -   PO Dist Failure 2632, in some embodiments failure of a purchase        order distribution;    -   PO Dist Service Lock 2634, in some embodiments locking of a        purchase order distribution service; and    -   PO Dist Service Instance 2636, in some embodiments an instance        of a purchase order distribution service.

FIG. 27 shows a database diagram 2700 including the transaction database228, and requisition database 2700 associated with the transactiondatabase.

In an embodiment, requisition database 2700 includes one or more of:

-   -   Req Config Section Title Help 2702, in some embodiments help        information for configuring a purchase requisition section        title;    -   Req Config Group Title Help 2704, in some embodiments help        information for configuring a purchase requisition group title;    -   Req Config Element Validation 2706, in some embodiments help        information for configuring a purchase requisition element        validation;    -   Req Config Section 2708, in some embodiments configuration of a        purchase requisition section;    -   Req Config Group 2710, in some embodiments configuration of a        purchase requisition group;

Req Config Element 2712, in some embodiments configuration of a purchaserequisition section element;

-   -   Req Config 2714, in some embodiments configuration of a purchase        requisition;    -   Req Config Version 2716, in some embodiments configuration of a        purchase requisition version;    -   Req File Data 2718, in some embodiments purchase requisition        file data;    -   Req Currency Exchange Rates 2720, in some embodiments purchase        requisition currency exchange rates;    -   Req Sup Dist Method Data 2722, in some embodiments data for a        purchase requisition distribution method;    -   Req Sup Dist Method 2724, in some embodiments a purchase        requisition distribution method;    -   Req WF Activity History 2726, in some embodiments purchase        requisition workflow activity history;    -   Req Audit Trail 2728, in some embodiments changes to a purchase        requisition for auditing purposes;    -   Req Summary 2730, in some embodiments a summary of a purchase        requisition;    -   Requisition 2732;    -   Req WF Activity Buffer 2734, in some embodiments a purchase        requisition workflow activity buffer;    -   Req User Selected Approver 2736, in some embodiments a purchase        requisition user-selected approver;    -   Supplier 2738;    -   Fulfillment Center 2740, in some embodiments a fulfillment        center for a purchase requisition;    -   Req Supplier Group 2742, in some embodiments a supplier group        for a purchase requisition;    -   Req Punchout Session 2744, in some embodiments a punchout        session for a purchase requisition;    -   Req CF Value Set Def 2746, in some embodiments for setting a        definition of a purchase requisition custom field value;    -   Req CF Value Set Ctxt 2748, in some embodiments for setting a        context of a purchase requisition custom field value;    -   Req CF Value Set Values 2750, in some embodiments for setting a        value of a purchase requisition custom field value;    -   Contract 2752;    -   Req Line Address 2756, in some embodiments an address line for a        purchase requisition;    -   Req Line Address Field 2758, in some embodiments an address        field line for a purchase requisition;    -   Req Line 2760, in some embodiments a line for a purchase        requisition;    -   Req Line Product 2762, in some embodiments a product line for a        purchase requisition;    -   Req Credit Card 2764, in some embodiments a credit card for a        purchase requisition;    -   Req Line Report 2766, in some embodiments a report line for a        purchase requisition;    -   Req Line Search 2768; in some embodiments a search line for a        purchase requisition; and    -   Req File Description 2770, in some embodiments a file        description for a purchase requisition.

FIG. 28 shows a database diagram 2800 including the transaction database228, and receipt database 2800 associated with the transaction database.

In an embodiment, receipt database 2800 includes one or more of:

-   -   Supplier 2802, in some embodiments a supplier for a receipt;    -   Receipt 2804;    -   Receipt Currency Exch Rates 2806, in some embodiments currency        exchange rates associated with a receipt;    -   Receipt PO Relship 2808, in some embodiments a relationship        between a purchase order and a receipt;    -   Receipt Summary 2810, in some embodiments a summary of a        receipt;    -   Req Line Address 2812, in some embodiments an address line for a        purchase requisition;    -   Receipt Line 2814;    -   General Product 2816; and    -   Receipt Line Inventory Replenishment 2818, in some embodiments        an inventory replenishment line for a receipt.

FIG. 29 shows a database diagram 2900 including the transaction database228, and sales order database 2900 associated with the transactiondatabase.

In some embodiments, the transaction database 228 and sales orderdatabase 2900 are accessed by transaction processing servers 223 andmiddleware/web methods servers 224.

In an embodiment, sales order database 2900 includes one or more of:

-   -   Order Config Section Title Help 2901, in some embodiments help        information for configuring a sales order section title;    -   Order Config Group Title Help 2902, in some embodiments help        information for configuring a sales order group title;    -   Order Config Element Validation 2903, in some embodiments        validation for configuring a sales order element;    -   Order File Description 2904;    -   Order File Data 2905;    -   Order Config Group 2906, in some embodiments configuration of a        sales order group;    -   Order Config Section 2907, in some embodiments configuration of        a sales order section;    -   Order Config Element 2908, in some embodiments configuration of        a sales order element;    -   Order Config Version 2909, in some embodiments configuration of        a sales order version;    -   Order Config 2910;    -   Order Summary 2911;    -   Order PO Clause 2912, in some embodiments a purchase order        clause;    -   Order Audit Trail 2913, in some embodiments changes for auditing        a sales order;    -   Order 2914;    -   Order WF Activity History 2915, in some workflow activity        history for a sales order;    -   Order CF Value Set Values 2916, in some embodiments values for a        sales order custom field;    -   Order CF Value Set Ctxt 2917, in some embodiments context for a        sales order custom field;    -   Order CF Value Set Def 2918, in some embodiments definition for        a sales order custom field;    -   Order Ext CF Values 2919;    -   Order Line Search 2920, in some embodiments a search line for a        sales order;    -   Order Line 2921;    -   Order Shipment 2922, in some embodiments a shipment for a sales        order;    -   Order Line Product 2923, in some embodiments a product for a        sales order;    -   Order Credit Card 2924, in some embodiments a credit card for a        sales order; and    -   Order Shipment Line 2925, in some embodiments a shipment line        for a sales order.

FIG. 30 shows a database diagram 3000 including the transaction database228, and workflow database 3000 associated with the transactiondatabase. In some embodiments, the transaction database 228 and workflowdatabase 3000 are accessed by transaction processing servers 223 andmiddleware/web methods servers 224.

As described, supplier users can access the catalog via themiddleware/web methods servers 224, which then forward the supplieraccess request to the custom database servers 222 and processing modulesfor execution, in order, for example, to update their own supplier data.End users may be able to search multiple suppliers within the catalogvia the end user interface 212, subject to access rules set by the superuser. End users may search the catalog for specific end user productrequirements via the middleware/web methods servers 224, which forwardthe end user search request to custom database servers 222 andprocessing modules for execution. Subsequently, the end user may theninvoke requisition and purchase orders via the middleware/web methodsservers 224, which forward the end user order to the transactionprocessing servers 223 for execution.

In an embodiment, workflow database 3000 includes one or more of:

-   -   Workflow Step 3002;    -   Workflow Step Attr Value 3004, in some embodiments an attribute        value for a workflow step;    -   Workflow Process Definition 3006;    -   Workflow Activity Attr Value 3008, in some embodiments an        attribute value for a workflow activity;    -   Workflow Activity Relship 3010, in some embodiments an        relationship for a workflow activity;    -   Workflow Activity 3012;    -   Workflow Folder Selection Rule 3014, in some embodiments a        selection rule for a workflow folder;    -   Workflow Activity Instance 3016, in some embodiments an instance        of workflow activity;    -   Workflow Folder Membership 3018, in some embodiments membership        of a workflow folder;    -   Workflow Folder 3020;    -   Workflow Folder Activity Instance 3022, in some embodiments an        activity instance for a workflow folder;    -   Users 3024;    -   Workflow Folder Robot Relship 3026;    -   Workflow Folder Entry 3028;    -   Workflow Robot 3030;    -   Workflow Robot Attr Value 3032;    -   Workflow Dynamic Rule Group 3034, in some embodiments an dynamic        rule group associated with the workflow;    -   Workflow Dynamic Rule Group Audit Trail 3036, in some        embodiments an audit trail for a dynamic rule group associated        with the workflow;    -   Workflow Dynamic Rule 3038;    -   Workflow Dynamic Rule Element 3040, in some embodiments an        element of a dynamic rule associated with the workflow; and    -   Workflow Dynamic Rule Audit Trail 3042, in some embodiments an        audit trail for a dynamic rule associated with the workflow.

FIG. 31 shows a database diagram 3100 including the staging database3100, and staging catalog database 3101, associated with the stagingdatabase 3100.

In an embodiment, the staging catalog database 3101 includes one or moreof a staging items database 3102, a staging price database 3131, and asummary search database 3130.

In an embodiment, staging items database 3102 includes one or more of:

-   -   Item Attribute Attr Value 3103, in some embodiments a value for        an item attribute;    -   Item Attribute Valid Values 3104, in some embodiments a set of        valid values for an item attribute;    -   Item Attribute Audit Trail 3105, in some embodiments an audit        trail for an item attribute;    -   Item Attribute Definition 3106, in some embodiments a definition        for an item attribute;    -   Item Attribute Data 3107, in some embodiments data for an item        attribute;    -   Item 3108;    -   Chem Structure 3109, in some embodiments a description of a        chemical structure that may be ordered through the procurement        system;    -   Chem Structure Supplier 3110, in some embodiments a supplier of        a chemical structure;    -   Item Chemical 3111 in some embodiments a commercial item of a        chemical structure e.g., a container of a certain chemical        structure;    -   Supplier 3112;    -   Item Image Description 3113, in some embodiments a description        of an image or picture associated with an item;    -   Item Image File Data 3114, in some embodiments an image data        file (e.g., a JPEG image or GIF image, as commonly used in web        applications);    -   Item Inventory Config 3115, in some embodiments data for        configuring inventory of an item; and    -   Item Inventory Config Audi Trail 3116, in some embodiments a        list of changes to data or an audit trail for configuring        inventory of an item.

In an embodiment, staging price database 3131 includes one or more of:

-   -   Items 3132;    -   Supplier 3133;    -   Item Attribute Audit Trail 3134, in some embodiments a list of        changes to data or an audit trail for an item attribute;    -   Price Set Org Details 3135, in some embodiments details of a        price setting organization;    -   Price Set 3136, in some embodiments a set price;    -   Price Version Approval 3137, in some embodiments approval for a        price version;    -   Price Version 3138;    -   Price Set Version 3139;    -   Price 3140;    -   Submission Price Component 3141;    -   Price Version Loading Submission 3142;    -   Submission Audit Trail 3143, in some embodiments a list of        changes to data or an audit trail for a submission; and    -   Submission 3144.

In an embodiment, summary search database 3130 includes one or more of:

-   -   Supplier Price Date 3117, in some embodiments a data associated        with a supplier price;    -   Supplier Content Date 3118;    -   Organization 3119;    -   Supplier 3120;    -   Searchable Verticals by Rule 3121, in some embodiments        supporting rule-based searching;    -   Product Rule 3122, in some embodiments a rule related to a        product;    -   Product Vertical 3123, in some embodiments supporting        product-based searching;    -   Org Supplier Item Counts 3124, in some embodiments a count of        items stored at an organization supplier;    -   Product Category 3125, in some embodiments a category related to        a product;    -   Supplier Category Summary 3126, in some embodiments a summary of        a supplier category;    -   Item Incr Indexing Queue 3127, in some embodiments a queue for        incrementally indexing items;    -   Org Favorites Full Indexing Queue 3128, in some embodiments a        full-indexing queue for organizational favorites; and    -   Org Favorites Incr Indexing Queue 3129, in some embodiments an        incremental-indexing queue for organizational favorites.

FIG. 32 shows a database diagram 3200 including the transaction database228, PO database 2500, buyer invoice database 3300, seller invoicedatabase 3400, requisition database 2700, receipt database 2800, salesorder database 2900, workflow database 3000, and contracts database3200, associated with the transaction database 228.

In an embodiment, the contracts database 3200 includes one or more of:

-   -   Supplier 3201;    -   Form Configuration 3202;    -   Contract Type 3203;    -   Contract Form Relationship 3204, in some embodiments an        relationship between a contract and a form;    -   Contract Scheduler Relationship 3205, in some embodiments an        relationship between a contract and a scheduler;    -   Contract Owner Relationship 3206, in some embodiments an        relationship between a contract and an owner;    -   Contract Department Relationship 3207, in some embodiments an        relationship between a contract and a department;    -   Contract Fulfillment Center Relationship 3208, in some        embodiments an relationship between a contract and a fulfillment        center;    -   Contract Audi Trail 3209, in some embodiments a list of changes        to data or an audit trail for a contract;    -   Contract Tier Info 3210, in some embodiments tier information        for a contract;    -   Contract Budget Actual 3211, in some embodiments an actual        budget for a contract;    -   User 3212; and    -   Department 3213.

FIG. 33 shows a database diagram 3300 including the transaction database228, PO database 2500, buyer invoice database 3300, seller invoicedatabase 3400, requisition database 2700, receipt database 2800, salesorder database 2900, workflow database 3000, and contracts database3200, associated with the transaction database 228.

In an embodiment, the buyer invoice database 3300 includes one or moreof:

-   -   Invoice Configuration Section Title Help 3301, in some        embodiments help information for configuring an invoice section        title;    -   Invoice Configuration Section 3202, in some embodiments        configuration of a invoice section;    -   Invoice Configuration 3203;    -   Invoice Configuration Group Title Help 3304, in some embodiments        help information for configuring an invoice group title;    -   Invoice Configuration Group 3305, in some embodiments        configuration of an invoice group;    -   Invoice Configuration Element Validation 3306;    -   Invoice Configuration Element 3307, in some embodiments        configuration of an invoice element;    -   Invoice Configuration 3308;    -   Invoice Configuration Version 3309;    -   Active Invoice Configuration Version 3310;    -   User Selected Approver 3311;    -   Currency Exchange Rates 3312;    -   Invoice Audit Trail 3313, in some embodiments a list of changes        (audit trail) to an item attribute for auditing purposes;    -   Invoice Summary 3314;    -   Invoice 3315;    -   Workflow Activity History 3316;    -   Supplier 3317;    -   Invoice Line 3318;    -   Remit to Address 3319;    -   Pending Actions 3320, in some embodiments pending actions        relating to an invoice;    -   Contract 3321;    -   PO 3322, in some embodiments a purchase order;    -   PO Line 3323, in some embodiments a purchase order line;    -   Invoice Line Product 3324, some embodiments a product line        relating to an invoice;    -   Invoice CF Value Set Def 3325, in some embodiments to set the        definition of a custom field value in an invoice;    -   Invoice CF Value Set Ctxt 3326, in some embodiments to set the        context of a custom field value in an invoice; and    -   Invoice CF Value Set Value 3327, in some embodiments to set the        value of a custom field value in an invoice.

FIG. 34 shows a database diagram 3400 including the transaction database228, PO database 2500, buyer invoice database 3300, seller invoicedatabase 3400, requisition database 2700, receipt database 2800, salesorder database 2900, workflow database 3000, and contracts database3200, associated with the transaction database 228.

In an embodiment, the seller invoice database 3400 includes one or moreof:

-   -   Invoice Configuration Section Title Help 3401, in some        embodiments help information for configuring an invoice section        title;    -   Invoice Configuration Group Title Help 3402, in some embodiments        help information for configuring an invoice group title;    -   Invoice Configure Element Validation 3403;    -   Invoice Configuration Section 3404, in some embodiments        configuration of an invoice section;    -   Invoice Configuration Group 3405, in some embodiments        configuration of an invoice group;    -   Invoice Configuration Element 3406, in some embodiments        configuration of an invoice element;    -   Invoice Configuration 3407, in some embodiments configuration of        an invoice;    -   Invoice Configuration Version 3409, in some embodiments        configuration version of an invoice;    -   Active Invoice Configuration Version 3410, in some embodiments        configuration of an active invoice;    -   Supplier 3411;    -   Currency Exchange Rates 3412, in some embodiments currency        exchange rates associated with an invoice;    -   Invoice 3413;    -   User Default Remit To Address 3414, in some embodiments a        default remit-to address for a user associated with an invoice;    -   Invoice Line 3415;    -   Remit To Address 3416, in some embodiments a remit-to address        associated with an invoice;    -   Invoice Line Product 3417; and    -   User 3418.

FIG. 35 shows a database diagram 3500 including the end user database232, associated with the user/security database 3500. In an embodiment,the user/security database 3500 includes one or more of:

-   -   User Info 3501, in some embodiments information relating to a        user;    -   User Permission Index 3502, in some embodiments an index of        permissions relating to a user;    -   User Audit Trail 3503, in some embodiments a list of changes        (audit trail) for a user for auditing purposes;    -   Users 3504;    -   User Attribute Value 3505, in some embodiments the value of an        attribute associated with a user;    -   User Role Membership 3506, in some embodiments membership        associated with a user role;    -   Organization 3507;    -   Organization Attribute Value 3508, in some embodiments a value        of an attribute associated with an organization;    -   Department 3509;    -   Position Department Relationship 3510, in some embodiments a        relationship between a position and a department;    -   Position Department Role Relationship 3511, in some embodiments        a relationship between a position and a department role;    -   Position 3512;    -   Role Attribute Value 3513, in some embodiments the value of an        attribute associated with a role;    -   Role 3514; and    -   Role Audit Trail 3515, in some embodiments a list of changes        (audit trail) for a role for auditing purposes.

FIG. 36 shows a database diagram 3600 including the scheduler database3600. In an embodiment, the scheduler database 3600 includes one or moreof:

-   -   Job Input Data 3601, in some embodiments data relating to a job        input;    -   Job Description 3602, in some embodiments a description relating        to a job;    -   Job Execution Instance 3603, in some embodiments an execution        instance relating to a job;    -   Job Input 3604;    -   Job Output 3605;    -   Trigger 3606;    -   Filed Description 3607;    -   Job Output Data 3608, in some embodiments data relating to a job        output;    -   File Data 3609;    -   Instance 3610; and    -   Lock 3611.

Each of the above identified elements may be stored in one or more ofthe previously mentioned memory devices, and corresponds to a set ofinstructions for performing a function described above. The aboveidentified modules or programs (i.e., sets of instructions) need not beimplemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various embodiments. In some embodiments, memory 2010 and2110 may store a subset of the modules and data structures identifiedabove. Furthermore, memory 2010 and 2110 may store additional modulesand data structures not described above.

FIG. 37 illustrates an exemplary new/non-catalog item administrativesetup tool in accordance with the present invention. The tool 3700 maybe used to configure the administrative preferences or options 3701 forthe new/non-catalog item feature that allows, for example, buyer usersof an organization with the capability of accessing the electronicprocurement system 20 (via the purchaser server application 1550 on thesystem side and a client application 1532 on the buyer side) toconfigure and add a new item (e.g., a good or service) to the masterproduct database 236. The new item may be stored, more specifically, forexample, in the items database 2401 of the catalog database 2400. Thepreferences or options 3701 of the tool 3700 may include, for example,supplier selection 3702, distribution 3703, or product details 3704. Inaddition, there may also be, for example, an option for enabling anon-catalog item entry 3705 or allowing non-catalog items by default forall suppliers 3706. The preferences or options of the supplier selection3702 may, for example, include: allowing users to choose from a list ofknown suppliers to associate with a new item; allowing users to manuallyenter ad-hoc suppliers to associate with a new item; or allowing usersto not specify a supplier. Further, the preferences or options ofdistribution 3703 may, for example, include permitting the expansion ofdistribution options by default. And, the preferences or options ofproduct details 3704 may, for example, include: allowing a zero pricefor a new item(s); allowing a blank catalog number for a new item;expanding the product details information by default; showing a productsize for the user; choosing a style associated with the display of theproduct size to the user; showing a flag to permit the user to designatethe item as taxable; showing a flag to permit the user to designate theitem as a capital expense; showing a commodity code to permit the userto designate a commodity code for the new item; showing a manufacturername to permit the user to designate a manufacturer name for the newitem; showing a manufacturer part number to permit the user to designatea manufacturer part number for the new item; showing an item flag topermit the user to designate specific item flags (e.g., additionaldescriptors) for the new item; showing a packaging amount to permit theuser to designate a packaging amount for the new item; or showing apackaging display style to permit the user to designate a packagingdisplay style for the new item.

FIG. 38 illustrates an exemplary new/non-catalog item access tool inaccordance with the present invention. The tool 3800 and its non-catalogitem option 3801 may be used to access the new/non-catalog item creationtool illustrated in the exemplary embodiment of FIG. 39. In addition tothe tool 3800, other tools of the system may also present an option thesame or similar to non-catalog option 3801 (e.g., a user may select thenon-catalog option 3801 to indicate that they want to add an item thatmay not be stored in a catalog of, for example, the master database 236or, more specifically, for example, the catalog database 2400; moreover,for example, a non-catalog item may be from a small/local supplier thatmay not be a supplier using the features of the electronic procurementsystem 20).

FIG. 39 illustrates an exemplary new/non-catalog item creation tool inaccordance with the present invention. The tool 3900, 3901 may be usedby users with appropriate privileges (as may be enforced by manageprivileges 1536; FIG. 15, 1536-A; FIG. 16, 1660, 1664) to describe andconfigure the new item that is to be added/stored to the master productdatabase 236 and, more specifically, may be stored in, for example, theitems database 2401 of the catalog database 2400; each of thesedatabases is accessible to all users with appropriate privileges withinthe same organization, as well as potentially by all users withappropriate privileges within an organization different from the one towhich the user who added the new item belongs (users may search for thenew item via at least the search engine 22, and in accordance withbusiness rules (e.g., based on cost, product type, or supplier; FIGS.8A-8D)). In some embodiments, the new item may be stored in a databaselocal to the user who added the item. Before the new item is stored in adatabase, a check is made to determine whether the new item is alreadystored in a database. If the new item is already stored in a database,then the user is notified via the tool 3900, 3901 by an appropriatemessage. The user may then reinitiate the process of adding the new itemwith a different configuration, or disregarding that new item as italready exists in a database. The tool 3901 may include, for example, afield for: describing the new item 3902, entering a catalog number toassign to the new item 3903, entering or choosing a product size 3904,entering a quantity for requisitioning/ordering 3905, entering a priceestimate 3906, entering a currency type (e.g., USD, EURO, YEN, etc.) forthe price estimate 3907, entering or choosing a packaging type (e.g.,EA) 3908. In another exemplary embodiment, the tool 3901 may furtherinclude, for example, a field for: a brand, a delivery date or time, areorder flag, supplier data, or shipping data. The user configuring theoptions for the new item may choose to view and associate productdetails 3912 with the new item. In addition, the user may or may notchoose to associate a supplier with the new item 3913. If the userchooses to associate a supplier with the new item, the user mayassociate either an existing or new supplier (FIG. 17; data on existingsuppliers is stored in the supplier database 1775); the user may also bepresented with an alternative supplier to the one chosen by the user toassociate with the new item. If the user does not associate a supplierwith the new item, then a user with appropriate privileges (e.g.,approver-level user, super user, or other similar user) in theorganization will be tasked and queried by the system to associate asupplier with the new item during the workflow process as the new itemproceeds to an approver, or before that time, in accordance withbusiness rules. A user may create a new item and quickly add another newitem for the same supplier without having to search for the samesupplier again, once a supplier has been associated with a new item.Also, a user may choose to not enter a catalog number 3903 (e.g., SKU)and force a search on the master product database 236 (the search may,for example, be run on the catalog database 2400). Further, a new itemthat is searched for and added to a cart by a user with appropriateprivileges, via the search engine 22 and cart and requisition tool 1100,respectively, is flagged as a new item for the purpose of routing thenew item appropriately, via the workflow management engine 1680 (FIG.16), during the workflow process of a purchase requisition/order to anappropriate approver and beyond in accordance with business rules. Ifthe item is approved for purchasing and a sales order is sent to theappropriate supplier(s), then similar routing patterns are followed fora workflow related to routing the sales invoice with the new item backto the appropriate user. At that time, the user may pay the amount dueon the invoice via, for example, the order/payment engine 1690 (FIG. 16)for the new item and other items that may also appear on the invoice.The appropriate supplier may then receive the payment via, for example,the receive payment engine 1780 (FIG. 17), and may then initiate theprocess of fulfilling the order via, for example, the sale fulfillmentengine 1770 and accordingly packaging the new item(s) (based on thepreferences specified in packaging 3908) and shipping the item(s) 1772.

The exemplary tools of FIGS. 37-39 may operate in the same or a similarmanner and be used to allow a user to configure and add a new supplierto the supplier database 1775. Moreover, like the process described forassociating a new, existing, or alternative supplier with a new item(see above), a new supplier may also be associated with either anexisting or new item. If a new supplier is added, the new supplier datamay then be stored accordingly in the supplier database 1775 or otherappropriate database.

FIG. 40 illustrates an exemplary form layout configuration tool inaccordance with the present invention. The tool 4000 and its formsconfiguration feature 4001 may be used to design and/or configure thelayout 4002 and elements 4003-4008 of a new or existing form. The formsconfiguration feature 4001 may also be used to build a new form byinvoking the build new form feature 4009. Once an existing form isconfigured or a new form is created, the preview form feature 4010 maybe invoked to view how the form is currently configured. Moreover, allof the existing forms (e.g., a form library) associated with the user orthe user organization may be displayed in the tree-like frame 4011 forthe user to choose from for further editing or configuration. Theexisting forms may be displayed in accordance with user privileges,organization privileges, or business rules, such that only theappropriate forms are displayed in the frame 4011. Moreover, layoutdetails may be configured via the layout details tool 4002. The layoutdetails tool 4002 may include, for example, the following elements forconfiguration and layout on a new or existing form: instructions 4003,supplier information 4004, order information 4005, personal information4006, sample 4007, or field views 4008. Order information 4005 mayinclude, for example, item, item information, service, serviceinformation, quantity 4016, price, currency, order date, delivery date,shipping date, priority, menu, privilege level, order size 4017, ororder type 4018. Similarly, order information 4005 may further include,for example, a title and help text section 4015 to accompany the new orexisting form. Also, field views 4008 may include, for example,unassigned form fields 4012, user defined form fields 4013, or allfields 4014. Unassigned form fields 4012 may include, for example, theelements: capital expense, catalog number, commodity code, contract,external attachments, form type, health and safety, internalattachments, manufacturer name, manufacturer part number, packaging,product description, product size, taxable, or UN/SPSC. Similarly, userdefined form fields 4013 may include, for example, the elements: textbox, numeric text box, unit price, check box, dropdown list, tab, frame,tree, multimedia component, scroll menu, check box, text area, radiobutton group, date, HTML area, link, image, or item list. Further, allfields 4014 may include, for example, the elements of unassigned formfields 4012 and user defined form fields 4013. All of these elements maybe customized for placement on a new or existing form in accordance withthe user's preferences; moreover, the elements may be pre-defined.

A user may first request to create a custom form for ordering an item(s)or searching for an item(s) via the build a new form feature 4009. Onlyusers with appropriate privileges will be permitted to create a customform; the user privileges may be enforced by manage privileges 1536. Ineither case, the appropriate database will be accessed and the form willeither be stored there, in the case of a new form, or a search query mayrun on the database based on the form, and search results returned tothe user. When a new form is created (or, an existing form is edited) atleast the forms database 2300 may be accessed; the master database 236and, more specifically, for example, the catalog database 2400 may alsobe accessed, including the items database 2401 or the prices database2430. Once invoked, the build a new form feature 4009 may present theuser with the layout details tool 4002 for customizing and configuringthe new form per the user's preferences (or, the organizations'preferences as well). For example, the user may choose to provideinstructions 4003 along with the form, in order to guide a user usingthe form on how to place orders using the form or, similarly, how toinvoke searches also using the form. In addition, a user may alsoprovide supplier information 4004 to accompany the form like, forexample, a supplier: name, address, telephone number, orderingpreferences, payment preferences, shipping preferences, or contractualpreferences. Furthermore, a user may also provide order information 4005to accompany the form like, for example, an order: quantity 4016, size4017, or type 4018. A user may also provide personal information 4006 toaccompany a form like, for example, name, title, department, address,telephone number, email, payment preferences, delivery preferences, orcontractual preferences. Moreover, a user may also provide a sample ofan item associated with the form via the sample 4007 element. All of theelements 4003-4008 of layout details 4002, or other elements notnecessarily shown in this exemplary embodiment, may be customized forplacement on the new or existing form in accordance with a user'spreference.

Once included, all of these form elements (above) may be filled-out orcompleted upon the creation of an instance of the form by a user withappropriate privileges, in accordance with business rules, who wishes toplace an order or search a database via the new or existing form.

FIG. 40A illustrates an exemplary form general configuration tool inaccordance with the present invention. The tool 4000A and its formgeneral configuration feature 4001A may be used to configure the generalfeatures of a new or existing form. The feature 4001A may display aversion date/time or a created by field. The user may input a versiondescription 4004A, or, if one is already available, then it wouldalready be displayed. The tool 4001A may also include a configurationparameters feature 4002A, which may further include, for example, theelements: form title 4005A, form type 4006A, limit supplier selectionoption 4007A, selected suppliers feature 4008A, currency 4009A, or fixeddistribution 4010A. The selected suppliers feature 4008A allows theaddition of suppliers to associate (or, add) with the new or existingform. Once added, the supplier(s) name and other relevant information,like, for example, address or telephone number are shown; a user maychoose to only associate a limited set of suppliers. Similarly, aselected contracts feature (not shown) may also allow the addition of acontract(s) to associate (or, add) with the new or existing form. Inparallel, with the contract management feature (discussed below), anappropriate contract may either be created or an existing contract maybe updated accordingly (e.g., tiers may be enforced, or special pricingmay be available, etc.); this may be done via the contact managementengine 1688, 1784 and contracts database 3200. Then, the configured formthat has been edited or created by the user may, for example, be storedin the forms database 2300 and may, for example, be managed by formmanagement 1693, 1783, or 1943, accordingly.

FIG. 41 illustrates an exemplary form user interface in accordance withthe present invention. The form user interface 4100 shown in theexemplary embodiment is actually an instance of a form configured usingthe features and elements described (see above) for the form layoutconfiguration tool 4000. The form user interface 4100 may include, forexample, a general instructions 4101 section, a supplier information4102 section, a personal information 4103 section, an order information4104 section, a sample 4105 section, or a total 4106 for the items. Thegeneral instructions 4101 section may include, for example, the list ofpersonnel eligible for ordering or searching for the item (e.g.,business cards) for which the form is customized (the list may be inaccordance with user privileges or business rules, as well). The sectionmay also include, for example, a note regarding the item (e.g., theidentification and title of individuals on business cards). Furthermore,the supplier information 4102 section may include, for example, thesupplier name, address, telephone number, and currency. The personalinformation 4103 section may include, for example, a name, title,department, street address, or email address. Moreover, the orderinformation 4104 section may include, for example, a quantity, ordersize, order type (e.g., new order, reorder of a previous order, orrevised reorder of a previous order). Finally, the sample 4105 sectionmay, for example, display an image (e.g., logo or trademark) or othermedia-type (e.g., movie, sound, slideshow, or other compatiblemedia-type) regarding the item being ordered or searched for. The samplemay also display a dynamically updated version of the actual item, ascustomized for a user (e.g., a business card with the user's custominformation). For example, a user may enter information into the formvia the form user interface 4100, which may then submit the informationto, for example, form management 1693 for processing; once processed byform management 1693, the information may accordingly be submitted tothe client application 1532 or, more specifically, for example, theweb-browser 1538, for presentation to the user in the sample 4105section of the form user interface 4100. The form user interface 4100may be coded/programmed for dynamic component display over theweb-browser 1538, such that the sample 4105 section of the form userinterface 4100 may be updated with the version of the actual item, ascustomized for a user; in other embodiments, other components of theform user interface 4100 may or may not be updated accordingly fordisplay via the client application 1532 or, more specifically, forexample, via the web-browser 1538. On the form user interface 4100, therequired fields (as customized by a user using the form layoutconfiguration tool 4000 or other similar tool of the system) are boldedor emphasized in some other way. Once the user is finishedcompleting/populating the form instance as displayed on the form userinterface 4100, or if the form attributes are pre-defined, the user mayproceed by (4107), for example, adding the form item(s) to a cart and:going to a cart, moving on to another form, customizing a new form, orsearching for a new form. Alternatively, the user may proceed by (4107),for example, storing the form item as a favorite for future use, suchthat the user does not have to re-populate the form (e.g., theattributes). The populated form may, for example, be stored in the formsdatabase 2300 and may, for example, be managed by form management 1693,1783, or 1943, accordingly.

FIG. 42 illustrates an exemplary form library interface in accordancewith the present invention. The form library interface 4200 and itsforms library feature 4201 may present for display and customizing theuser's own forms 4202, user organization's forms 4203, or another user'sor organization's forms (not shown). The forms library feature 4201 mayin conjunction with the forms database 2300 and form management 1693,1783, or 1943 logically link new or existing forms for organized storageand user/organization access. For example, if an organization is asubsidiary or a parent corporation, partnership, or other businessentity, it may wish to share forms with its related business entities.Similarly, organization with close business relationships may wish to dothe same; and, users within the same department, group, or local officemay also wish to share forms. The forms library (or, logically linkedforms) may be organized hierarchically (e.g., based on a designated formtype). Forms may include, for example, organization forms 4204 (e.g., abid service request, a general service request, or a non-catalog itemform), contract forms 4205, human resources forms 4206,services-configurable forms 4207 (e.g., business cards, catered lunch,or ordering catered lunch), services-facilities 4208 (e.g., telephone,lighting, etc.), services-IT 4209 (network, computer, etc.), servicesmiscellaneous 4210, or services-print and marketing 4211. Otherdesignated form types may also be created and may be associated with theuser's or organization's business rules, as well as those business rulesassociated with the item(s) or supplier(s) associated with the form.Similarly, the workflow management engine 1680, 1930 may interface withform management 1693, 1783, 1943 to associate one or more workflows witha form or designated form type. Such workflows may also include dynamicworkflows (FIG. 30) accessible via the workflow database 3000.

FIG. 43 illustrates an exemplary forms search results interface inaccordance with the present invention. The forms search resultsinterface 4300 and its search results feature 4301 may present searchresults for display and selection by the user. Forms may be found insearch results (e.g., a search for business cards) 4303-4305 along withother items not associated with forms. Forms may be assigned searchablekeywords for the search engine 22 to better be able to locate thoseforms. A user may select 4306 forms only, forms in addition to othersearch results, or just other search results. Once selected, the usermay add the form(s) or other search result(s) to a new or existing cart4302 (implemented via, for example, workflow management 1680, 1930,2142, sales/purchase management 2046 or, more specifically, for example,cart management 1683, 2144) for the purpose of, for example, separatingforms from other item search results or for further ordering orcheckout; a user may also choose, for example, to compare two or moreselections 4302.

FIG. 44 illustrates an exemplary user-defined searchable attributesconfiguration interface in accordance with the present invention. Theuser-defined searchable attributes configuration tool 4400 may includean attribute search 4401 tool for defining the detailed configuration ofthe custom search field or attribute to be added by a user (implementedvia, for example, the catalog engine 1655, 1755, 2020, 2120 or, morespecifically, search 1659, catalog updates 1759, 1822, or user localcatalog create/access module 2024, 2122). The added or edited customsearch field or attribute may be accessible via the master database 236,catalog database 2400 and, more specifically, for example, via the formsdatabase 2300, items database 2401 or prices database 2430; the customsearch field or attribute may also be accessible via the transactiondatabase 228 and, more specifically, for example, via the purchase orderdatabase 2500 (including, for example, the fax database 2600, revisionsdatabase 2602, or distribution database 2604), requisition database2700, receipt database 2800, buyer invoice database 3300, sales invoicedatabase 3400, sales order database 2900, workflow database 3000, orcontracts database 3200. Moreover, the added or edited custom searchfield or attribute may be accessed and managed by, for example, thesearch engine 22. For example, the search engine 22 may run a searchquery against the catalog database 2400 and, more specifically, forexample, against the items database 2401 or prices database 2430 when auser inputs a specific value in the added or edited custom search field.The search results are then returned and displayed to the user via asearch results interface (e.g., FIG. 43).

The attribute search 4401 tool for defining the detailed configurationof the custom search field or attribute to be added by a user withappropriate privileges (as may be enforced by manage privileges 1536;FIG. 15, 1536-A; FIG. 16, 1660, 1664) include, for example, a create newattribute feature 4403 for creating and defining new searchable field orattributes, an apply all changes feature 4404 for applying any changesmade to a searchable field or attribute, a details feature 4402 fordefining the detailed configuration 4405, validation configuration 4407,search/display configuration 4408, or display text and helpconfiguration 4406, of the searchable field or attribute. The detailedconfiguration 4405 may allow a user to define, for example, the internalname of the field or attribute (e.g., keyword), the organization (e.g.,“owner”) that has control over the field or attribute, an associatedcatalog (e.g., via a catalog name or number), the data type associatedwith the field or attribute (e.g., text, whole number, floating pointnumber, Boolean, multi-select, etc.), whether the field or attribute maybe multi-valued, or whether the field or attribute is active orinactive. Furthermore, the validation configuration 4405 may allow auser to define, for example, what to do if the value entered is too long(e.g., accept save, reject save, notify user, etc.), what to do if thevalue does not match the list of field values (e.g., accept save, rejectsave, notify user, etc.), or the present field size limit (which can beincreased or decreased accordingly). The search/display configuration4408 may include, for example, an option for whether the field orattribute is: searchable by itself (via its own search field), includedin the keyword index (for searching via the keyword index field),included in the part number index (for searching via the part numberfield), or included in the supplier name index (for searching via thesupplier name index field); the field or attribute may be searchable viaall three of these options. The display text and help configuration 4406of the searchable field or attribute may include, for example, a featurefor using a default text and help configuration, a display name for thesearchable field or attribute (i.e., how it appears to a user via asearch interface or otherwise via another interface of the system), helptext associated with using the searchable field or attribute, a languageto display the searchable field or attribute in accordance with (e.g.,English, Japanese, Dutch, German, Arabic, Italian, Greek, French, orother supported language), and a feature for enabling or disabling eachof display name, help text, or language.

FIG. 45 illustrates an exemplary user-defined searchable attributes itemassignment interface in accordance with the present invention. Theuser-defined search attributes item assignment interface tool 4500 maybe used to assign (or associate) 4502 a searchable field or attribute toa specific item(s) (or, in an alternative embodiment, a user,organization, supplier, or purchase/sale). That is, once assigned (4503,4504) and provided with one or more values, the searchable field orattribute may be used by the search engine 22 to search the appropriatedatabase(s) (or, database index) (described above) for more efficientlyretrieving the specific item(s) (or, in an alternative embodiment, auser, organization, supplier, or purchase/sale) according to thesearchable field or attribute.

FIG. 46 illustrates an exemplary search interface with user-definedsearchable attributes in accordance with the present invention. Thesearch interface with user-defined searchable attribute tool 4600 mayinclude, for example, a product (or, item—e.g., good or service)interface 4601. The interface 4601 may display the searchable field(s)or attribute(s) 4602 such that a user may input a value to be used bythe search engine 22 for searching against the appropriate database(s)(described above). Whether a searchable field or attribute 4602 appearson the interface 4601 depends on whether the appropriate option wasselected during the configuration of the search/display 4408 (e.g.,searchable by itself) and the detailed configuration 4405 (e.g., activeor inactive); these options may be edited initially when the searchablefield or attribute is configured 4401, 4402 or dynamically at a latertime.

FIG. 47 illustrates an exemplary contract general setup interface inaccordance with the present invention. The contract general setupinterface 4700 may include, for example, a contract general setup tool4701, a display of the contract identifier 4702, or a display of thecontract supplier 4703. The contact management engine 1688, 1784implements the features of the contract general setup interface 4700 andmay access the contracts database 3200 (which may contain many contractsor, possibly, no qualified contracts) during theimplementation/execution of these features embodied. The contractgeneral setup tool 4701 may be used for entering the most relevant andnecessary information regarding a contract between one or morebuyer/purchasing organization and one or more supplier/sellingorganization. After the information is entered, it may be saved forfuture access by users; moreover, an existing contract's information maybe updated via the tool 4701 and renewed 4704. The contract generalsetup interface tool 4701 may include, for example, the followingcontract general setup features, elements, or options: a contract name4705, a contract number 4706, a currency 4707, a supplier name 4708, anactive option 4709, an apply automatically option 4710, a description4711, an effective dates feature 4715, an effective date 4712, anexpiration date 4713, a time zone 4714, a delivery date, a prioritylevel, a billing/shipping address, a billing method, a renewals feature4720, an auto-renew option 4716, a renewal term 4717, a maximum renewals4718, a renewal number 4719, a notification lead times feature 4724, aneffective lead time 4721, an expiration lead time 4722, or a renewallead time 4723. For example, a contract name 4705, contract number 4706,currency 4707, or supplier name 4708 are used to describe importantelements of a contract stored, or to be stored, in the contract database3200; such a contract may later be assigned to a form (see above) or maybe updated in accordance with amendments or contractual events (e.g.,termination/expiration, escalation terms, meeting one or more tier(s)level—then, e.g., offering rebates or price reductions, assignment,unenforceability, material breach, etc.) that might occur throughout theterm of the contract. Moreover, for example: the active option 4709 maydenote whether the contract is active or inactive; the applyautomatically option 4710 may denote whether changes/updates to thecontract (or, related ones) should be applied automatically; thedescription 4711 may provide a description related to the contract; theeffective dates feature 4715 may be used to designate an effective date4712 and an expiration date 4713, and the time zone 4714 may relate tothe effective dates feature 4715 for accurate determination of theeffective 4712 and expiration 4713 dates; the renewals feature 4720 maybe used to denote terms associated with contract renewal like, forexample, whether the contract should be automatically renewed uponexpiration (via the auto-renew option 4716), what the renewal term 4717should be (e.g., 1 year, 1 month, 1 week, 1 day, etc.), the maximumrenewals 4718 permitted, and which renewal number 4719 the contract iscurrently in; the notification lead times feature 4724 may be used toprovide an effective date lead time 4721 value (e.g., hours, days,weeks, months, or years) for notification (via, for example, email,telephone, facsimile, text message, multimedia message, mail, carrier,or other method of communication) of the effective date to those users,organizations, or suppliers associated with a contract (similarly, anexpiration lead time 4722 value or a renewal lead time 4723 value fornotification may be specified via the notification lead times feature4724).

FIG. 48 illustrates an exemplary contract details setup interface inaccordance with the present invention. The contract details setupinterface 4800 may include, for example, a contract details setup tool4801. The contract details setup tool 4801 may include, for example, adetails feature 4802 for entering contract information for reference.The details feature 4802 may include, for example, a details textsection 4803, searchable keywords 4804 (e.g., for locating a contract insearches, as applied to a general search or contact specific search), adesignation of the hard copy location 4805 of the contract, a featurefor attaching/linking and uploading/downloading (e.g.,importing/exporting) a copy (or, URL—Unifonn Resource Locator—or otheraddress) of the contract (e.g., soft copy) 4806, a feature forattaching/linking and uploading a copy (or, URL, or other address) of acontract's supporting documentation (e.g., soft copy) 4807, theprojected savings associated with the contract 4808, the contract type(e.g., requirements contract) 4809, a designation of a blanket purchaseorder 4810 to be applied to the contract, a purchase order number 4811associated with the contract, a visibility controls feature 4812, an enduser visibility type 4813 for designating the end user type(s) (e.g.,buyer, supplier, or organization) for which the contract isvisible/accessible, or a contract owners type 4814 for designating theother contract owner(s) (e.g., buyer, supplier, or organization) forwhich the contract is visible/accessible and editable according to theuser status as an owner with, presumably, higher privileges.

FIG. 49 illustrates an exemplary purchase order-to-contract associationinterface in accordance with the present invention. The purchaseorder-to-contract association interface 4900 may include a purchaseorder (PO) clauses tool 4901 that allows, for example, adding clauses,defining the added clauses, and assigning/associating the clauses to oneor more contracts that could be sent with each PO to a supplier withwhich the contract(s) may be associated. The PO clauses tool 4901 mayinclude, for example, an add clauses feature 4902 for adding clauses, anassigned PO clauses feature 4903 for displaying and accessing thepurchase order clauses that may be assigned to a contract(s), or afeature for acting on selected PO clauses 4904 (e.g., by adding,deleting, or editing selected clauses). The assigned PO clauses feature4903 may include, for example, a clause number 4905, a clause name 4906,a clause text 4907, or a select clause option 4908. The features of tool4901 may be leveraged for purchase requisitions, sales orders, salesinvoices, or buyer invoices, as well as purchase orders, if necessary(this may hold true for the other contract-related features describedherein).

FIG. 50 illustrates an exemplary forms-to-contract association interfacein accordance with the present invention. The forms-to-contractassociation interface 5000 may include, for example, a forms-to-contractassociation tool 5001 for associating a form (e.g., item form, supplierform, etc.) to one or more contracts via the contract engine 1554 (or,specifically, for example, the contract management engine 1688, 1784,2060, 2160 and, more specifically, via the associate contract with formsmodule 2068, 2168). Once a form (e.g., custom to a specific supplier orgeneric to one or more suppliers) is associated with one or morecontracts, the form may be accessed when the contract is viewed eitherin a contract search interface (FIG. 57) or, alternatively, when asupplier contract pop-up (or, other type of window or interface) isinvoked for viewing one or more contracts associated with a supplier4703. Moreover, using the search engine 22, and displayed, for example,via a search results interface 4300, one or more forms may be shown insearch results according to keyword attributes (e.g., search criteria)that may be associated with one or more contracts or forms; that is, theassociation of a contract and a form may permeate the search feature, orother features of the system, for example, for seamless integration andassociation. To implement these features, the forms-to-contractassociation tool 5001 may include, for example, an add form feature 5002for adding a new or existing form to associate with one or morecontracts, a view/list forms feature 5003 for viewing/listing the addedforms for associating with one or more contracts, a nickname 5004element for viewing the available forms for association by a nickname, aprice estimate 5005 element for viewing the price estimate (in U.S.Dollars (USD), or other currency) that may correspond to an availableform, or a remove form feature 5006 for removing an added form from thelist of available forms.

FIG. 51 illustrates an exemplary contract owner's interface inaccordance with the present invention. The contract owner's interface5100 may include, for example, a contract owner's tool 5101 forassociating one or more contract owners to one or more contracts via thecontract engine 1554 (or, more specifically, for example, the contractmanagement engine 1688, 1784). A contract owner associated with one ormore contracts may, for example, edit or manage the contract, or receivenotifications (via, for example, email, telephone, facsimile, textmessage, multimedia message, mail, carrier, or other method ofcommunication) related to the contract (e.g., when amendments are madeor contractual events occur). The contract owner's tool 5101 may, forexample, include an add owner feature 5102 for adding one or more ownersas owners associated with one or more contracts, a view/list ownersfeature 5103 for viewing/listing the added owners for associating withone or more contracts, an owner name element 5104 for viewing theassociated owners by name, a username 5105 element for viewing theassociated owners by nickname, an email 5106 element for viewing theemail of the associated owners, a telephone number 5107 for viewing thetelephone number of the associated owners, and a remove feature 5108 forremoving one or more associated owners from being associated with one ormore contracts.

FIG. 52 illustrates an exemplary contract budget interface in accordancewith the present invention. The contract budget interface 5200 mayinclude, for example, a contract budget tool 5201 for setting contractbudgets, limits, spending tiers to trigger contractual events (e.g.,rebates or price reductions), or document types (e.g., purchaserequisition (PR), purchase order (PO), or invoice) associated withreceiving notifications of tier or budget achievements. The contractbudget tool 5201 may be implemented via the contract engine 1554 (or,more specifically, for example, the contract management engine 1688,1784). Furthermore, the contract budget tool 5201 may include, forexample, a contract budget feature 5202 for configuring the contractbudget elements and for implementing features of the contract budgettool 5201. The contact budget feature 5202 may include, for example, atotal current budget element 5203 for setting a total current budgetassociated with a contract, an actual PR spend element 5204 forpresenting the actual purchase requisition amounts (e.g., spent, to bespent, etc.), an actual PO spend element 5205 for presenting the actualpurchase order amounts (e.g., spent, to be spent, etc.), an actualinvoice spend element 5206 for presenting the actual invoice amounts(e.g., spent, to be spent, etc.), a tier information feature 5207 forconfiguring tiers (e.g., spending threshold triggers for rebates, pricefluctuations, price reductions, etc.), a use multiple tiers feature 5208for denoting whether to use one or more tiers, a tier type feature 5209for denoting the tier type (e.g., percentage, whole number/dollar, etc.)associated with one or more tiers, a tier element 5210 for presentingthe present (or, past or future) tiers, a tier ceiling element 5211 forsetting a tier ceiling/limit (for example, a dollar amount, possiblybased on one or more currencies; or, for example, a quantity or timelimit/period), an incentive element 5212 (in, for example, a percentageor dollar amount, possibly based on one or more currencies), adescription element 5213 for describing a tier ceiling/limit and theincentive that may be associated with a tier, a document tiernotification feature 5214 for configuring which documents (PR, PO, orinvoice) tier/budget notifications may apply to, a PR documentnotification element 5215 for sending notifications associated withpurchase requisitions, a PO document notification element 5216 forsending notifications associated with purchase orders, an invoicedocument notification element 5217 for sending notifications associatedwith invoices.

FIG. 53 illustrates an exemplary contract user criteria interface inaccordance with the present invention. The contract user criteriainterface 5300 may include, for example, a contract user criteriafeature 5301 for configuring which user(s) within an organization mayaccess or use one or more contracts. The contract user criteria feature5301 may be implemented via the contract engine 1554 (or, morespecifically, for example, the contract management engine 1688, 1784).Moreover, the contract user criteria feature 5301 may include, forexample, an owner filter feature 5302 for designating that only ownersmay access a contract, a department filter feature 5303 for designatingwhether one or more available departments 5304 may access a contract5305. The contract user criteria feature 5301 may be used fordesignating that an entire organization, a specific department, contractowners, individual users, or any combination of theseorganizations/departments/owners/user, may have access to a contract.

FIG. 54 illustrates an exemplary contract other criteria interface inaccordance with the present invention. The contract other criteriainterface 5400 may include, for example, a contract other criteriafeature 5401 for configuring which users of an available fulfillmentaddress may access or use one or more contracts. The contract othercriteria feature 5401 may be implemented via the contract engine 1554(or, more specifically, for example, the contract management engine1688, 1784). Moreover, the contract other criteria feature 5401 mayinclude, for example, a fulfillment address filter feature 5402 fordesignating that only users at one or more available fulfillmentaddresses 5403 may access a contract 5404.

FIG. 55 illustrates an exemplary contract history interface inaccordance with the present invention. The contract history interface5500 may include, for example, a contract history tool 5501 for trackingand viewing contractual amendments or events. The contract history tool5501 may be implemented via the contract engine 1554 (or, morespecifically, for example, the contract management engine 1688, 1784). Auser or organization may use the contract history tool 5501 forhistorical tracking or auditing purposes. The contract history tool 5001may include, for example, a contract history feature 5503 for actualviewing or access to the contractual amendment or events associated withone or more contracts 5504. The tool 5001 may also be used for exporting(e.g., downloading or transmitting via other electronic communicationmeans) contract history(ies) for tracking or auditing purposes.Moreover, a contract history search tool 5502 may be used to search forcontracts based on type, date, user, organization, supplier,effective/expiration date(s), tier(s), ceiling(s)/limit(s), or item(s).Once the search engine 22 receives the appropriate search query from thecontract history tool 5502, contract history search results may bepresented via the interface 5504.

FIG. 56 illustrates an exemplary contract price sets interface inaccordance with the present invention. The contract price sets interface5600 may include, for example, a pricing tool 5601, which may furtherinclude a contract price sets tool 5602 for assigning one or more pricesets to one or more contracts, in accordance with access to the one ormore contracts (see above; FIGS. 53-54). The contract price sets tool5502 may be implemented via the contract engine 1554 (or, morespecifically, for example, the contract management engine 1688, 1784).Furthermore, the contract price sets tool 5602 may include, for example,a price sets feature 5603 for presenting available price sets that maybe assigned to one or more contracts. The available price sets aresearchable (via search engine 22 receiving queries from price set searchtool 5605); search results received from search engine 22 may then bedisplayed via a price sets search results interface 5604. The price setssearch results interface 5604 may include, for example, a total numberof results found 5606, a supplier associated with a price set 5607, aprice set name 5608, a currency associated with a price set 5609, acontract name/nickname associated with a price set 5610, a price settype associated with a price set 5611, or an edit price sets feature forediting a price set 5612.

FIG. 57 illustrates an exemplary contract search interface in accordancewith the present invention. The contract search interface 5700 mayinclude, for example, a contract search tool 5701 for searching for oneor more contracts according to one or more search criteria 5702. Thecontract search tool 5701 may be implemented via the contract engine1554 (or, more specifically, for example, the contract management engine1688, 1784). The search criteria 5702 (e.g., contract number 5704,contract keyword 5705, or supplier/catalog name 5706) may be transformedinto one or more search queries for processing by the search engine 22.Some or all of the search criteria may be selected from within theseveral respective databases of the system (described above); forexample, the search criteria 5702 may include, for example, a selectsupplier feature 5707 for selecting one or more suppliers from thesupplier database 1775 (or, another database of the system) forsearching. Users may be able to search for or view the contracts towhich they may have access (see above; FIGS. 53-54). Aftersearching/processing, the search engine 22 may return the search resultsto the contract search tool 5701, which may include a contract searchresults interface 5703 for displaying the one or more contract searchresults 5708. The contract search results interface 5703 may include,for example, a number of contracts found 5709, a contract number foreach search result 5710, a renewal number for each search result 5711, asupplier name associated with a contract for each search result 5712, acontract name for each search result 5713, an effective date for eachsearch result 5714, an expiration date for each search result 5715, oran active/inactive indicator for each search result 5716.

FIG. 58 illustrates an exemplary contract view interface in accordancewith the present invention. The contract view interface 5800 mayinclude, for example, a contract view tool 5801 for viewing detailedinformation regarding a contract. The contract view tool 5801 may beimplemented via the contract engine 1554 (or, more specifically, forexample, the contract management engine 1688, 1784); a contract viewedusing the contract view tool 5801 may be stored in the transactionsdatabase 228 and, more specifically, the contracts database 3200. Thecontract view tool 5801 may include, for example, a contract informationfeature 5802 or also a contract controls feature 5803. The contractinformation feature 5802 may include, for example, a general informationfeature 5804 for displaying general information elements like, forexample, a contract name, a contract number, a supplier name associatedwith the contract, an active/inactive flag for indicating whether acontract is currently in an active or inactive state, an applyautomatically flag for indicating whether amendments or contractualevents associated with the contract are applied automatically, adescription of the contract, or an effective and expiration dateassociated with the contract; the contract information feature 5802 mayalso include, for example, a detailed information feature 5805 fordisplaying detailed information (see above; FIG. 40) like, for example,a hard copy location of a contract, a soft copy location of a contract,any supporting documents associated with the contract, a projectedsavings percentage/amount associated with the contract, or a contracttype associated with the contract; the contract information feature 5802may further include, for example, a budget information feature 5806 fordisplaying budget information (see above; FIG. 52) like, for example, abudget total amount, whether the contract has multiple tiers, an actualpurchase requisitions amount associated with the contract, an actualpurchase order amount associated with the contract, or an invoice actualamount associated with the contract; or, the contract informationfeature 5802 may further include, for example, a blanket purchase order(PO) information feature for displaying blanket PO information like, forexample, a blanket PO number to use for a contract. Moreover, thecontract controls feature 5803 (see above; FIG. 51) may provideinformation related to who may exercise some level of control over acontract. The contract controls feature 5803 may include, for example, acontracts owners information feature 5808 for displaying informationassociated with who the contract owners may be, an applicable usersfeature 5809 for displaying elements indicating whether the contract maybe used only by owners (or, other as well) and whether/which departments(see above; FIG. 53) may access the contract, an applicable productsfeature 5810 for displaying a fulfillment address (see above; FIG. 54)that may be associated with products associated with the contract, a POclauses feature 5811 for displaying any applicable PO clauses (seeabove; FIG. 49) that may be associated with the contract, or a formsfeature 5812 for displaying any forms that may be associated with thecontract (see above; FIG. 50).

FIG. 59 illustrates an exemplary contract pricing interface inaccordance with the present invention. The contract pricing interface5900 may include, for example, a contract pricing tool 5907. Thecontract pricing tool 5901 may be implemented via the contract engine1554 (or, more specifically, for example, the contract management engine1688, 1784). Furthermore, the contract pricing tool 5907 may display,for one or more selected items/products, the pricing available to aspecific user/organization. To access the contract pricing tool 5907associated with one or more items/products, a user may first search forthe item/product via a product search tool 5901 that may present theuser with additional search tools 5902; the product search tool 5901 andits additional search tools 5902 may send search queries to the searchengine 22 for the search engine to execute against one or morerespective databases (e.g., master product database 236, transactiondatabase 228, or more specific databases); search results 5906 are thenreturned and presented; by default, the lowest price for eachitem/product may be displayed in search results. Once a user hasselected one or more items/products and invoked a select price orcontract feature, then the user may access the contract pricing tool5907. Like the search results 5906, by default, the contract pricingtool 5907 may display the lowest price for one or more items/productsselected and available 5908 to a user (the tool 5907 may also displayany discounts related to a price set); available prices may be organizedaccording to owner price, department price, organization price,corporate list price, or an option for setting a manual price (in anappropriate currency) 5909. Thus, one or more prices may be assigned tothe same contract but may be available to various levels of users,departments, organizations (may include a corporate list price), or maybe manually set by each in accordance with user privileges or businessrules. A user may select a specific price and proceed to checkout viathe cart feature; the price selected for the item/product of a contractmay further be applied to the user, department or organization inaccordance with user privileges or business rules.

FIG. 60 illustrates an exemplary contract search interface in accordancewith the present invention. The contract search interface 6000 mayinclude, for example, a contract search interface 6001, which mayfurther include additional search tools 6002, 6003 for locating one ormore contracts stored in the transactions database 228 (or, morespecifically, for example, the contracts database 3200) via the searchengine 22. The contract search tool 6001 may be implemented via thecontract engine 1554 (or, more specifically, for example, the contractmanagement engine 1688, 1784 and the search engine 22). A user may inputa search query with keywords or criteria that may be associated with oneor more contracts for which the user would like to locate. The searchengine 22 may then receive a search query from the search tools 6002,6003 to execute against the appropriate database(s) (see above) andreturn one or more matches 6004, 6005 via the contract search interface6000, 6001. Forms associated with a contract may also be searched forusing the interface 6000, 6001, in addition to the forms searchinterface (discussed above). A user may then choose to select one ormore contracts displayed in the interface 6000, 6001 for further accessto the details of the one or more contracts as implemented via thecontract view tool 5801, pricing via the contract pricing tool 5901, orother available feature of the system.

Further to the configure and add new item feature(s) of the presentinvention is a feature for accessing an existing contract or creating anew contract that may be associated to one or more items via itemattributes. The tools (described below) of this feature may beimplemented, for example, via the contract engine 1554 (or, morespecifically, for example, the contract management engine 1688, 1784).The item attributes may be defined and used by a user of an organizationto associate one or more contracts with one or more items (or, itemattributes). The item attributes that may be used to associate itemswith contracts may be, for example, a stock keeping unit (SKU), acatalog number, a unit of measure (UOM), a color, a packaging, a origin,a manufacturer identification, a description, or other identifier. Otheritem attributes may also be used in a similar way without departing fromthe scope of the present invention. Each one of these item attributes,alone or in combination, may be used to associate items with contracts.Items may be considered a match with items of one or more contracts ifthe item attributes that are filled-in/completed match those of theitems in the one or more contracts. That is, for example, a subset ofthe entire item attributes may match with that of the items of one ormore contracts. Item attributes, in addition to or as an alternative toitems, may also be associated with contracts. And, contracts may bebetween user organizations and suppliers (for items from, for example,supplier catalogs, whether hosted or punch-out catalogs). Items may benon-catalog items, items from forms (discussed in more detail above),items from hosted catalogs, items from punch-out catalogs, and/or itemsfrom other sources.

When, for example, a user adds one or more items (or, items associatedwith one or more item attributes) to one or more shopping carts (managedvia, for example, the workflow management engine 1680 or, morespecifically, for example, the cart management engine 1683), an existingor created contract is accessed and applied to the shopping cart itemsor the one or more requisitions that may result from the addition of theitems to one or more shopping carts. The application of a contract tothe items of one or more shopping carts is executed in accordance withbusiness rules (managed via, for example, the business rules engine 24)to determine if, for example, the contract is available to the userand/or the items match those of the contract. Subsequently, when apurchase order is created for the respective items and shopping carts,for example, it is created in accordance with the one or more terms ofthe one or more applicable contracts that may apply (and, for example,the contract number may be applied to each item of a requisition,purchase order, and invoice). If, for example, one or more items orshopping carts do not invoke the application of one or more contracts,then a contract is not applied and default workflow and business rulesmay be applied. Moreover, when a item is added to a shopping a cart, theitem's price (and, related data) may be compared with the price andother related terms of the one or more applicable contracts (e.g.,between a user's organization and the one or more applicable supplier orsupplier catalogs, whether hosted or punch-out catalogs). The item'sprice used to compare against the one or more potentially applicablecontract prices is obtained from, for example, the applicable supplier'scatalog (stored in, for example, the master database 235 or, morespecifically, for example, the catalog database 2400).

In some instances, for example, the process of associating items withcontracts can be done manually through the end user interface 212 or,alternatively or in addition, through one or more electronic files whosedata is imported into the system. The determination of which items toassociate with which contracts using one or more specific itemattributes may be performed according to several conflict handling rulemechanisms (implemented via, for example, the contract. First, forexample, if a match exists between one or more items (or, itemattributes) and the corresponding items (or, item attributes) of acontract, the contract is associated (or, populated) with the respectiveitem data that may be associated with one or more items. Second, forexample, if more than one match exists (e.g., the same SKU but adifferent/inconsistent UOM than that outlined in the contract), theneither the user may be prompted to select from a list of potentiallymatching items or the contract may be auto-populated according to, forexample, default rules or business rules. A user's item selection(s) forassociation with one or more contracts may override the exact match orno match scenarios described; in that instance, the user should haveappropriate level permissions and the match should be in accordance withbusiness rules. Moreover, a user may choose to remove the association ofa specific item (or, item attribute) with one or more contracts, inaccordance with business rules; the respective user's permission levelwould have to be set to a level high enough (e.g., an administratoruser's level) in order for the user to be able to remove suchassociations.

Furthermore, a price validation feature may be invoked manually by theuser or automatically upon the loading of items (or, item attributes)for association with one or more contracts. The price validation featureperforms an analysis to ensure that the attribute data associated withan item, as retrieved for a hosted catalog, punch-out catalog (or otheritem data source), properly corresponds to the respective item attributedata of one or more applicable contracts with which the item may beassociated. The validation feature may ensure that the creation ofpurchase requisitions and, subsequently, purchase orders is performedaccurately and in accordance with the appropriate terms of the one ormore applicable contracts. Moreover, the price validation feature mayalso ensure that users are presented with the most accurate itemattribute data (or, other related data like, for example, price) priorto reaching the requisition or purchase order stage in the workflowprocess (e.g., of one or more transactions). A special algorithm mayperform the operations of the price validation feature. Some of thealgorithm's operations may include, for example, (1) an operation forcomparing the price of an item with the one or more appropriatecontracts prior to permitting user access to that item (e.g., forrequisitions and purchasing), (2) an operation for annotating one ormore items as price matches/mismatches to the extent that the item pricematches the price of one or more appropriate contracts, and (3) anoperation for determining the extent of such price mismatches accordingto one or more metrics like actual deviation, percentage deviation, orother appropriate metric. Users may configure one or more business rulesfor accepting or rejecting items whose deviations falls within a certaintolerance, in comparison to the one or more contracts with which theitems may be associated. Furthermore, in some embodiments, an inaccurateitem attribute may reach a further stage in the workflow process, suchas the stage where invoices are created, but even at that stage in theworkflow process the inaccuracy may be detected and raised for the userto choose a course of action. Potential courses of action for the userto choose from may include, for example, (1) correct inaccuracymanually, (2) correct inaccuracy automatically by associating the one ormore inaccurate item attributes with the one or more accurate itemattributes according to the closest matches from potentially associatedcontracts, (3) ignore inaccuracy, or (4) abolish current transaction andstart a new transaction.

In addition to the many features above that are related to associatingcontracts with one or more item attributes, the search features of thepresent invention (described in more detail above) may also leverage theavailability of item attributes for executing search queries. Forexample, item attributes may be used to search for the one or morecontracts that may be associated with the respective attributes. Inaddition, for example, a smart algorithm may be implemented fordetermining which item attributes may be associated with one or morecontracts depending on the respective terms of those contracts, even ifno such association pre-exists. Other smart algorithms of similar typemay also be implemented without departing from the scope of the presentinvention.

FIG. 63 illustrates an exemplary add products to contract interface inaccordance with the present invention. The add products to contractinterface 7400 may include, for example, an add products to contracttool 7401 (implemented via, for example, the contract engine 1554 or,more specifically, for example, the contract management engine 1688,1784)). The add products to contract tool 7401 may, for example, provideusers with the necessary features and tools 7404, 7414 for entering itemattributes 7408-7413 (e.g., catalog number 7408, description 7409,supplier size 7410, supplier packaging 7411, color 7412, contract unitprice 7413) and adding 7404 (or, associating) the corresponding item(s)to a contract 7415. Multiple items with overlapping item attributes mayalso be added, while the non-overlapping item attributes may be used todifferentiate among the items. An item price 7413 entered via the enteritem attributes tool 7404, 7414 may override the price associated withthe item when obtained from a supplier 7416 or catalog.

FIG. 64 illustrates an exemplary auto look-up catalog items interface inaccordance with the present invention. The auto look-up catalog itemsinterface 7500, 7508 may include, for example, an auto look-up ofcatalog items tool with a single item match 7500 (e.g., illustrating asingle item match) and an auto look-up of catalog items tool withmultiple items match 7508 (e.g., illustrating multiple item matches).The tools may be implemented via for example, the contract engine 1554or, more specifically, for example, the contract management engine 1688,1784. The tool with a single item match 7500 may include, for example, acatalog number entry 7501, a description entry 7502, a supplier sizeentry 7503, a supplier packaging entry 7504, a color entry 7505, acontract unit price entry 7506, and a match status feature 7507. Thematch status feature 7507 provides dynamically updated informationregarding the results of a look-up executed against one or more catalogswith matching entry data 7501-7506 (e.g., a matching catalog number,etc.) The match status feature 7507 may identify the matching catalog(from, for example, the catalog database 2400) for the entered matchingentry data 7501-7506 (or, a subset thereof) and may also provide a userwith appropriate permissions access to the catalog in accordance withbusiness rules. Once provided with access, the user may confirm theappropriate item match from the appropriate catalog. Alternatively, orin addition, if the feature 7507 automatically makes an exact match, thematch status feature 7507 may then return the respective entry data7501-7506 from the appropriate catalog and automatically populate theentries of the tool 7500. Moreover, the tool with multiple items match7508 may include, for example, a catalog number entry 7509, adescription entry 7514, a supplier size entry 7515, a supplier packagingentry 7516, a color entry 7517, a contract unit price entry 7518, and amatch status feature 7510-7513. The match status feature 7510-7513 forthe tool 7508 may identify one or more catalogs for the entered matchingentry data 7509, 7514-18 (or, a subset thereof) and may also provide auser with appropriate permissions access to the catalog in accordancewith business rules. Once provided with access, the user may confirm theappropriate one or more item matches from the appropriate catalog. Uponconfirmation of a user's selection of one or more item matches, fromeither the tool with a single item match 7500 or the tool with multipleitems match 7508, the respective entry data for the item(s) is returned,populates the entries of the tools 7501-7506, 7509, 7514-7518, and isassociated with the appropriate contract (e.g., 7415).

FIG. 65 illustrates an exemplary add/remove multiple products to/fromcontract interface in accordance with the present invention. Theadd/remove multiple products to/from contract interface 7600 mayinclude, for example, a recently added products tool 7601 for displayingthe most recently added products/items to a contract (e.g., 7415). Thetool 7601 (implemented via for example, the contract engine 1554 or,more specifically, for example, the contract management engine 1688,1784) provides a user with the capability to further add additionalproducts/items 7602 to a contract and also the capability to removeproducts/items 7603 shown as recently added to a contract.Products/items that are designated for removal 7603 are disassociatedfrom the contract with which they were associated (e.g., 7415). Productsthat are disassociated form the contract with which they were associatedmay later be retrieved and associated with the contract and/or adifferent contract.

FIG. 66 illustrates an exemplary search and display assigned productsinterface in accordance with the present invention. The search anddisplay assigned products interface 7700 may include, for example, asearch and display contract products/item tool 7701 (implemented via,for example, the search engine 22) for searching for one or moreproducts/items associated with a contract 7703 using search criterialike, for example, a catalog number 7704 and/or description 7705associated with the products/items. The search results returned by thesearch engine 22 after executing the search query using the one or moresearch criteria may then be returned to the tool 7701 for display in oneor more GUI components 7702 (e.g., a list/table of the number ofproducts) on the user interface 212. For example, a list/table of thenumber of products found 7702 may include the following item attributes:a catalog number 7706, a description 7707, a supplier size 7708, asupplier packaging 7709, a color 7710, and/or a contract unit price7711. Moreover, each item in the list/table 7702 may also include aselect item box 7712 for designating the user's selection of theparticular item for further processing according to additional features7713 of the present invention (discussed for FIG. 67).

FIG. 67 illustrates an exemplary remove assigned products interface inaccordance with the present invention. The remove assigned productsinterface 7800 may include, for example, a remove selected/all tool7801. The remove selected/all tool 7801 (implemented via for example,the contract engine 1554 or, more specifically, for example, thecontract management engine 1688, 1784) may include features for removingthe association of all selected 7802 products/items to a contract 7803.The tool 7801 provides users with the ability to remove the associationof multiple selected 7802 products/items to a contract 7803 using oneinvocation of the tool 7801. In addition, the association of allproduct/items to a contract 7803 may be removed using one invocation ofthe tool 7801. The erroneous removal of the association ofproducts/items to a contract 7803 may be alleviated using, for example,the add products to contract tool 7401 (described above).

FIG. 68 illustrates an exemplary validate and import products interfacein accordance with the present invention. The validate and importproducts interface 7900, 7910 may include, for example, a validateproducts tool 7900 and an import products tool 7910. The tools may beimplemented via, for example, the auxiliary services module 2090, 2184,and/or web browser 2118. The validate products tool 7900 may include,for example, a recent activity summary tool 7903 and a contract productsimport/export request tool 7902. The validate products tool 7900utilizes the recent activity summary tool 7903 to illustrate thevalidation procedure's results to a user over the user interface 212. Inorder to invoke the validation features of the tool 7900, the user mayfirst selection the validate option from the actions menu 7904 of thecontract products import/export request tool 7902. Alternatively, thevalidation features of the tool 7900 may also be invoked automaticallyupon the selection of the import option from the actions menu 7904. Anyerrors that are identified during the validation procedure may bedisplayed via the recent activity summary tool 7903; further, an errorfile may be created and the erroneous entries of the file will behighlighted in some form. The user may be prompted via the userinterface 212 to download the error file. The user may then choose toedit the error file, correct any errors, and attempt to import 7904,7910 the file 7911 for validation once again. Recent activity (e.g.,completion date, request date, master contract, total records, recordsvalidated/imported, records with warning, and/or records witherrors/duplicates) regarding the status of importation activity may bedisplayed via the recent activity summary tool 7912. At least onebenefit of importing a file with one or more validated products/items(stored in, for example, the master database 235 or, more specifically,for example, the catalog database 2400) for association with a contract7907 (using, for example, the import products tool 7910) may be theefficiency of importing 7904 the validated products/items (and theirattributes) using a single invocation of the validate products tool 7900prior to importation. In another instance, items/products and theirattributes may be exported 7904 (using, for example, the contractproducts import/export request tool 7902; see also, for example, FIG.69) for editing or storage, for example, and/or subsequent importation7904 and association with the same or different contract 7907. Yetagain, upon importation, the validation features of the presentinvention would be invoked.

FIG. 61 is a flowchart representing a server method for SKU basedcontract management. For example, the flowchart illustrates thecomputer-implemented steps of, at a server system hosting an electronicprocurement system: receiving a user request for access to the system;granting access to a user; receiving a user request to access or createa contract between a user organization and a supplier or catalog; andreceiving a user request to associate a specific item attribute to thecontract.

FIG. 61A is a flowchart representing a server method for shopping cartand price validation features of SKU based contract management. Forexample, the flowchart illustrates the computer-implemented steps of, ata server system hosting an electronic procurement system: receiving auser request for access to the system; granting access to a user;receiving a user request to add a item to a shopping cart; andassociating the item to a contract.

FIG. 62 is a flowchart representing a client method for SKU basedcontract management. For example, the flowchart illustrates thecomputer-implemented steps of, at a client system communicating with anelectronic procurement system: sending a user request for access to thesystem; receiving access to the system; sending a user request to accessor create a contract between a user organization and a supplier orcatalog; and sending a user request to associate a specific itemattribute to the contract.

FIG. 70 illustrates an exemplary field management interface inaccordance with the present invention, as described. A LanguageSelection is illustrated, including a ‘select a language’ option forselecting a language for use in the electronic procurement system. AField Management selection is illustrated, allowing a user to selectfields from a field selection menu, showing a field history, and showingoptions for creating a new sibling or a new child. A ‘save option’ andan ‘apply all changes’ option is shown also.

FIG. 71 illustrates an exemplary update favorite(s) process flow inaccordance with the present invention, as described. An option isprovided for a user to select a favorite description, which may beapplied to a product, and which may be placed in a favorites menu.

FIG. 72 illustrates an exemplary document setup interface in accordancewith the present invention, as described. An option to add internalattachments is shown. An option to add attachments for all suppliers isshown.

FIG. 73 illustrates a system 10300 hosted at a supplier server 10310,which interacts over a network 16 with a plurality of purchaser clients212, both as described earlier. The purchaser clients run clientapplications 1532. This application may include a web-browser interfaceor a stand alone application, for accessing the supplier electronicprocurement service 10320 and server 10330. The server 10330 may providea web interface 10350 as describe earlier. The electronic procurementprovider 10320 hosts a plurality of databases 10360, including databases2200 as described earlier.

FIG. 74 illustrates a system 10400 hosted at a purchaser server 10410,which interacts over a network 16 with a plurality of supplier clients214, both as described earlier. The supplier clients run clientapplications 1516. This application may include a web-browser interfaceor a stand alone application, for accessing the purchaser electronicprocurement service 10420 and server 10430. The server 10430 may providea web interface 10450 as describe earlier. The electronic procurementprovider 10420 hosts a plurality of databases 10460, including databases2200 as described earlier.

In some embodiments, the electronic procurement system 20 is a singleinstance multi-tenant system. In some embodiments the electronicprocurement system 20 is a web-based system.

In some embodiments the electronic procurement system 20 is locatedindependently from suppliers and purchasers of the electronicprocurement system. In some embodiments the electronic procurementsystem 20 is located at a supplier of the electronic procurement system.In some embodiments the electronic procurement system 20 is located at apurchaser of the electronic procurement system.

It will be apparent to those skilled in the art that variousmodifications and variations can be made to the present inventionwithout departing from the spirit or scope of the invention. Thus, it isintended that the present invention cover the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

We claim:
 1. A computer-implemented method, comprising: at a serversystem hosting an electronic procurement system, the server systemincluding a processor and a memory storing programs for execution by theserver system: receiving a user request to associate one or more itemattributes with a contract between a user organization and a supplier orcatalog, wherein an item attribute describes an item characteristicwithout specifying a particular catalog item; associating the one ormore item attributes with the contract; and after associating the one ormore item attributes with the contract.